For me, the lines blur between coding standards and coding guidelines. We have (internally developed) coding standards that address both formatting (comment structure, variable naming conventions, and other 'readability' aspects) and technical content (when to unroll loops, etc.).
Review checklists guide the code reviewer in assessing code; e.g., it outlines things to check for, both compliance to the standards (code structure, etc.) and technical (use of literals instead of defines, array / loop indices, etc.).
Just to round it out, there are also code inspections. These are more formal checks for bugs rather than compliance to conventions. We often facilitate these with a checklist as well. These focus on just the technical aspects identifying bugs.