![\"Headings](\"https:\/\/softchalkcloud.com\/lesson\/files\/ZEQwxjK8lbSPHW\/head_fig2.gif\")
\r\nGeneral Guidelines for Headings<\/h2>\r\nHeadings are so important that there are a number of guidelines that deal with heading content, level, language use, and conventions.\r\nHeading Content<\/h3>\r\n\r\n \t- Use headings to identify the major sections and subsections of a report.<\/li>\r\n \t
- Make headings indicate the range of topic coverage in the section. For example, if the section covers the\u00a0design\u00a0and\u00a0operation\u00a0of a pressurized water reactor, the heading \"Pressurized Water Reactor Design\" would be incomplete and misleading, since it does not include the concept of operation.<\/li>\r\n<\/ul>\r\n
Heading Level<\/h3>\r\n\r\n \t- Use a different style for each level of heading: main headings within the text (not the same as the title), second level, third level, etc. That does not always mean that you need to use different fonts; you can choose different sizes, colors, or capitalization. Apply each heading style consistently throughout the document.<\/li>\r\n \t
- Consider \u201crun-in\u201d headings (words in bold or color that actually start a sentence) only if you have a lot of heading levels. Run-in headings can help you avoid the problem of too many lower-level headings looking alike.<\/li>\r\n \t
- Use actual headings as much as possible instead of bold or italic text, for accessibility.<\/li>\r\n<\/ul>\r\n
Heading Language<\/h3>\r\n\r\n \t- Use specific, self-explanatory language in headings. For example, instead of \"Background\" or \"Technical Information,\" use \"Physics of Fiber Optics.\"<\/li>\r\n \t
- When possible, omit articles from the beginning of headings to be as concise as possible. For example, \"The Pressurized Water Reactor\" can easily be changed to \"Pressurized Water Reactors.\"<\/li>\r\n \t
- Use parallel phrasing in the same level of heading, e.g., all -ing words, or all noun phrases.<\/li>\r\n<\/ul>\r\n
Heading Conventions<\/h3>\r\n\r\n \t- Avoid stacked headings\u2014any two consecutive headings without intervening text.<\/li>\r\n \t
- Avoid a lone heading by itself without another like it in the same section. If you don't have enough content for two headings, then you may not need a heading.<\/li>\r\n \t
- Avoid \"widows and orphans\" in headings, when a heading occurs at the bottom of a column or page and the text it introduces starts at the top of the next column or page. Make sure to have at least two lines of text after the heading if the heading occurs toward the end of a page, or else put the heading and its text on a new page.<\/li>\r\n \t
- Avoid pronoun reference to headings. For example, if you have a heading \"Torque,\" don't begin the sentence following it with something like \"This is a physics principle.....\" Don't assume that a reader will relate the pronoun \"this\" to the heading \"Torque.\"<\/li>\r\n \t
- Don't use headings as titles for tables or figures.<\/li>\r\n<\/ul>\r\n
\r\n \t- \u00a0A very general guideline for reports and longer documents is to have two-three headings per regular page of text. Note that this is a guideline only, but you get the idea that you should have a few sections and headings on most pages of text in longer documents, as opposed to either a block of text, or too many sections and headings.<\/li>\r\n<\/ul>\r\nCheck out the Purdue Online Writing Lab page on APA Headings and Seriation<\/a> for details and examples of headings in APA style.\r\n
<\/figure>\r\nCommon Problems with Headings<\/h2>\r\nProblems occur with headings when they are too wordy, not parallel in language, not clearly representative of their information, or not comply with general heading guidelines in some way.\u00a0 The following diagram points out some common heading problems.\r\n<\/figure>\r\n![\"Common](\"https:\/\/softchalkcloud.com\/lesson\/files\/ZEQwxjK8lbSPHW\/heading_prob2.jpg\")
<\/figure>\r\n\r\ntry it<\/h3>\r\nTechnical writers themselves fall into errors with headings. Look at the page on Memos: Purpose and Format<\/a> in a Technical Writing text. See how many errors with headings you can identify, and explain how each error could be corrected.\r\n\r\n[reveal-answer q=\"1\"] Compare your Answer [\/reveal-answer]\r\n[hidden-answer a=\"1\"]\r\n\r\n \t- The first two headings are stacked - there is no text between the main heading \"Memos: Purpose and Format\" and the next heading \"Memos.\" There is no need for the \"Memos\" heading; correct the stacked headings by eliminating \"Memos.\"<\/li>\r\n \t
- \"Five Tips for Effective Business Memos\" is a main heading. However, the main heading for the page indicates only two second-level headings, Purpose and Format. The \"Five Tips\" section does include a tip on format, but also includes a wider range of tips that deal with content and language. In this case, the main heading might be edited to be more inclusive, e.g., \"Writing Effective Memos.\" Then the page could logically include three second-level headings.<\/li>\r\n \t
- There's another set of stacked headings with \"Five Tips\" and \"Audience Orientation.\" Insert some text here.<\/li>\r\n \t
- The headings that come after \"Five Tips\" are visually at the same level as \"Five Tips,\" in the same size and bold blue type. Yet these headings (\"Audience Orientation,\" \"Professional Formal Tone,\" etc.) should be third-level headings, since they offer specific tips.\u00a0 Correct them by differentiating them in size and color.<\/li>\r\n<\/ol>\r\n[\/hidden-answer]\r\n\r\n<\/div>\r\n ","rendered":"
![\"\"](\"https:\/\/s3-us-west-2.amazonaws.com\/courses-images\/wp-content\/uploads\/sites\/5366\/2020\/07\/22130609\/136-300x185.jpg\")
<\/p>\n
Headings are very useful in technical writing. They:<\/p>\n
\n- offer main concepts succinctly<\/li>\n
- alert readers to upcoming topics and subtopics<\/li>\n
- break up long stretches of text<\/li>\n
- help readers locate specific information quickly<\/li>\n
- make the text easy to navigate<\/li>\n<\/ul>\n
As a reader, look at the Environmental Health<\/a> page from the U.S. Department of Health and Human Services’ Healthy People site. Headings make it easy to see the scope of information on the page, as well as locate a section of information that interests you. Headings make the page readable and accessible.<\/p>\nHeadings are also useful to you as a writer. They keep you organized and focused on the topic. When you begin using headings, your impulse may be to create headings\u00a0after\u00a0you’ve written the rough draft. Instead, anticipate the headings\u00a0before\u00a0you start the rough draft, and use them to keep you on track as you write. If you outline your document, you can often extract headings from your outline, as headings are main ideas.<\/p>\n
<\/p>\n
General Guidelines for Headings<\/h2>\n
Headings are so important that there are a number of guidelines that deal with heading content, level, language use, and conventions.<\/p>\n
Heading Content<\/h3>\n\n- Use headings to identify the major sections and subsections of a report.<\/li>\n
- Make headings indicate the range of topic coverage in the section. For example, if the section covers the\u00a0design\u00a0and\u00a0operation\u00a0of a pressurized water reactor, the heading “Pressurized Water Reactor Design” would be incomplete and misleading, since it does not include the concept of operation.<\/li>\n<\/ul>\n
Heading Level<\/h3>\n\n- Use a different style for each level of heading: main headings within the text (not the same as the title), second level, third level, etc. That does not always mean that you need to use different fonts; you can choose different sizes, colors, or capitalization. Apply each heading style consistently throughout the document.<\/li>\n
- Consider \u201crun-in\u201d headings (words in bold or color that actually start a sentence) only if you have a lot of heading levels. Run-in headings can help you avoid the problem of too many lower-level headings looking alike.<\/li>\n
- Use actual headings as much as possible instead of bold or italic text, for accessibility.<\/li>\n<\/ul>\n
Heading Language<\/h3>\n\n- Use specific, self-explanatory language in headings. For example, instead of “Background” or “Technical Information,” use “Physics of Fiber Optics.”<\/li>\n
- When possible, omit articles from the beginning of headings to be as concise as possible. For example, “The Pressurized Water Reactor” can easily be changed to “Pressurized Water Reactors.”<\/li>\n
- Use parallel phrasing in the same level of heading, e.g., all -ing words, or all noun phrases.<\/li>\n<\/ul>\n
Heading Conventions<\/h3>\n\n- Avoid stacked headings\u2014any two consecutive headings without intervening text.<\/li>\n
- Avoid a lone heading by itself without another like it in the same section. If you don’t have enough content for two headings, then you may not need a heading.<\/li>\n
- Avoid “widows and orphans” in headings, when a heading occurs at the bottom of a column or page and the text it introduces starts at the top of the next column or page. Make sure to have at least two lines of text after the heading if the heading occurs toward the end of a page, or else put the heading and its text on a new page.<\/li>\n
- Avoid pronoun reference to headings. For example, if you have a heading “Torque,” don’t begin the sentence following it with something like “This is a physics principle…..” Don’t assume that a reader will relate the pronoun “this” to the heading “Torque.”<\/li>\n
- Don’t use headings as titles for tables or figures.<\/li>\n<\/ul>\n
\n- \u00a0A very general guideline for reports and longer documents is to have two-three headings per regular page of text. Note that this is a guideline only, but you get the idea that you should have a few sections and headings on most pages of text in longer documents, as opposed to either a block of text, or too many sections and headings.<\/li>\n<\/ul>\n
Check out the Purdue Online Writing Lab page on APA Headings and Seriation<\/a> for details and examples of headings in APA style.<\/p>\n<\/figure>\nCommon Problems with Headings<\/h2>\n
Problems occur with headings when they are too wordy, not parallel in language, not clearly representative of their information, or not comply with general heading guidelines in some way.\u00a0 The following diagram points out some common heading problems.<\/p>\n<\/figure>\n<\/figure>\n\ntry it<\/h3>\n
Technical writers themselves fall into errors with headings. Look at the page on Memos: Purpose and Format<\/a> in a Technical Writing text. See how many errors with headings you can identify, and explain how each error could be corrected.<\/p>\n Compare your Answer <\/span><\/p>\n\n\n- The first two headings are stacked – there is no text between the main heading “Memos: Purpose and Format” and the next heading “Memos.” There is no need for the “Memos” heading; correct the stacked headings by eliminating “Memos.”<\/li>\n
- “Five Tips for Effective Business Memos” is a main heading. However, the main heading for the page indicates only two second-level headings, Purpose and Format. The “Five Tips” section does include a tip on format, but also includes a wider range of tips that deal with content and language. In this case, the main heading might be edited to be more inclusive, e.g., “Writing Effective Memos.” Then the page could logically include three second-level headings.<\/li>\n
- There’s another set of stacked headings with “Five Tips” and “Audience Orientation.” Insert some text here.<\/li>\n
- The headings that come after “Five Tips” are visually at the same level as “Five Tips,” in the same size and bold blue type. Yet these headings (“Audience Orientation,” “Professional Formal Tone,” etc.) should be third-level headings, since they offer specific tips.\u00a0 Correct them by differentiating them in size and color.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n
<\/p>\n\n\t\t\t \n\t\t\t Candela Citations<\/h3>\n\t\t\t\t\t \n\t\t\t\t\t\t \n\t\t\t\t\t\t\t CC licensed content, Original<\/div>- Headings, adapted from Open Technical Communication; attributions below. Authored by<\/strong>: Susan Oaks. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>CC licensed content, Shared previously<\/div>
- Headings (pages 1-4). Authored by<\/strong>: David McMurrey & Cassandra Race. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/ZEQwxjK8lbSPHW\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- Page Design (page 2 of 6). Authored by<\/strong>: David McMurrey and Jonathan Arnett. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/GZgMx1yw3kRhzL\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- image of file folders with tabs for headings. Authored by<\/strong>: Ulrike Mai . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/hanging-files-filing-cabinet-1920437\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li><\/ul><\/div>\n\t\t\t\t\t\t <\/div>\n\t\t\t\t\t <\/div>\n\t\t\t <\/section>","protected":false},"author":81366,"menu_order":3,"template":"","meta":{"_candela_citation":"[{\"type\":\"original\",\"description\":\"Headings, adapted from Open Technical Communication; attributions below\",\"author\":\"Susan Oaks\",\"organization\":\"Empire State College, SUNY\",\"url\":\"\",\"project\":\"Technical Writing\",\"license\":\"cc-by-nc\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"Headings (pages 1-4)\",\"author\":\"David McMurrey & Cassandra Race\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/ZEQwxjK8lbSPHW\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"Page Design (page 2 of 6)\",\"author\":\"David McMurrey and Jonathan Arnett\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/GZgMx1yw3kRhzL\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of file folders with tabs for headings\",\"author\":\"Ulrike Mai \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/hanging-files-filing-cabinet-1920437\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"}]","CANDELA_OUTCOMES_GUID":"","pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-202","chapter","type-chapter","status-publish","hentry"],"part":193,"_links":{"self":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/users\/81366"}],"version-history":[{"count":14,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202\/revisions"}],"predecessor-version":[{"id":1678,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202\/revisions\/1678"}],"part":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/parts\/193"}],"metadata":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/media?parent=202"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapter-type?post=202"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/contributor?post=202"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/license?post=202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- \r\n \t
- Use headings to identify the major sections and subsections of a report.<\/li>\r\n \t
- Make headings indicate the range of topic coverage in the section. For example, if the section covers the\u00a0design\u00a0and\u00a0operation\u00a0of a pressurized water reactor, the heading \"Pressurized Water Reactor Design\" would be incomplete and misleading, since it does not include the concept of operation.<\/li>\r\n<\/ul>\r\n
Heading Level<\/h3>\r\n
- \r\n \t
- Use a different style for each level of heading: main headings within the text (not the same as the title), second level, third level, etc. That does not always mean that you need to use different fonts; you can choose different sizes, colors, or capitalization. Apply each heading style consistently throughout the document.<\/li>\r\n \t
- Consider \u201crun-in\u201d headings (words in bold or color that actually start a sentence) only if you have a lot of heading levels. Run-in headings can help you avoid the problem of too many lower-level headings looking alike.<\/li>\r\n \t
- Use actual headings as much as possible instead of bold or italic text, for accessibility.<\/li>\r\n<\/ul>\r\n
Heading Language<\/h3>\r\n
- \r\n \t
- Use specific, self-explanatory language in headings. For example, instead of \"Background\" or \"Technical Information,\" use \"Physics of Fiber Optics.\"<\/li>\r\n \t
- When possible, omit articles from the beginning of headings to be as concise as possible. For example, \"The Pressurized Water Reactor\" can easily be changed to \"Pressurized Water Reactors.\"<\/li>\r\n \t
- Use parallel phrasing in the same level of heading, e.g., all -ing words, or all noun phrases.<\/li>\r\n<\/ul>\r\n
Heading Conventions<\/h3>\r\n
- \r\n \t
- Avoid stacked headings\u2014any two consecutive headings without intervening text.<\/li>\r\n \t
- Avoid a lone heading by itself without another like it in the same section. If you don't have enough content for two headings, then you may not need a heading.<\/li>\r\n \t
- Avoid \"widows and orphans\" in headings, when a heading occurs at the bottom of a column or page and the text it introduces starts at the top of the next column or page. Make sure to have at least two lines of text after the heading if the heading occurs toward the end of a page, or else put the heading and its text on a new page.<\/li>\r\n \t
- Avoid pronoun reference to headings. For example, if you have a heading \"Torque,\" don't begin the sentence following it with something like \"This is a physics principle.....\" Don't assume that a reader will relate the pronoun \"this\" to the heading \"Torque.\"<\/li>\r\n \t
- Don't use headings as titles for tables or figures.<\/li>\r\n<\/ul>\r\n
- \r\n \t
- \u00a0A very general guideline for reports and longer documents is to have two-three headings per regular page of text. Note that this is a guideline only, but you get the idea that you should have a few sections and headings on most pages of text in longer documents, as opposed to either a block of text, or too many sections and headings.<\/li>\r\n<\/ul>\r\nCheck out the Purdue Online Writing Lab page on APA Headings and Seriation<\/a> for details and examples of headings in APA style.\r\n
<\/figure>\r\n Common Problems with Headings<\/h2>\r\nProblems occur with headings when they are too wordy, not parallel in language, not clearly representative of their information, or not comply with general heading guidelines in some way.\u00a0 The following diagram points out some common heading problems.\r\n
<\/figure>\r\n <\/figure>\r\n\r\ntry it<\/h3>\r\nTechnical writers themselves fall into errors with headings. Look at the page on Memos: Purpose and Format<\/a> in a Technical Writing text. See how many errors with headings you can identify, and explain how each error could be corrected.\r\n\r\n[reveal-answer q=\"1\"] Compare your Answer [\/reveal-answer]\r\n[hidden-answer a=\"1\"]\r\n
- \r\n \t
- The first two headings are stacked - there is no text between the main heading \"Memos: Purpose and Format\" and the next heading \"Memos.\" There is no need for the \"Memos\" heading; correct the stacked headings by eliminating \"Memos.\"<\/li>\r\n \t
- \"Five Tips for Effective Business Memos\" is a main heading. However, the main heading for the page indicates only two second-level headings, Purpose and Format. The \"Five Tips\" section does include a tip on format, but also includes a wider range of tips that deal with content and language. In this case, the main heading might be edited to be more inclusive, e.g., \"Writing Effective Memos.\" Then the page could logically include three second-level headings.<\/li>\r\n \t
- There's another set of stacked headings with \"Five Tips\" and \"Audience Orientation.\" Insert some text here.<\/li>\r\n \t
- The headings that come after \"Five Tips\" are visually at the same level as \"Five Tips,\" in the same size and bold blue type. Yet these headings (\"Audience Orientation,\" \"Professional Formal Tone,\" etc.) should be third-level headings, since they offer specific tips.\u00a0 Correct them by differentiating them in size and color.<\/li>\r\n<\/ol>\r\n[\/hidden-answer]\r\n\r\n<\/div>\r\n ","rendered":"<\/p>\n
Headings are very useful in technical writing. They:<\/p>\n
- \n
- offer main concepts succinctly<\/li>\n
- alert readers to upcoming topics and subtopics<\/li>\n
- break up long stretches of text<\/li>\n
- help readers locate specific information quickly<\/li>\n
- make the text easy to navigate<\/li>\n<\/ul>\n
As a reader, look at the Environmental Health<\/a> page from the U.S. Department of Health and Human Services’ Healthy People site. Headings make it easy to see the scope of information on the page, as well as locate a section of information that interests you. Headings make the page readable and accessible.<\/p>\n
Headings are also useful to you as a writer. They keep you organized and focused on the topic. When you begin using headings, your impulse may be to create headings\u00a0after\u00a0you’ve written the rough draft. Instead, anticipate the headings\u00a0before\u00a0you start the rough draft, and use them to keep you on track as you write. If you outline your document, you can often extract headings from your outline, as headings are main ideas.<\/p>\n
<\/p>\nGeneral Guidelines for Headings<\/h2>\n
Headings are so important that there are a number of guidelines that deal with heading content, level, language use, and conventions.<\/p>\n
Heading Content<\/h3>\n
- \n
- Use headings to identify the major sections and subsections of a report.<\/li>\n
- Make headings indicate the range of topic coverage in the section. For example, if the section covers the\u00a0design\u00a0and\u00a0operation\u00a0of a pressurized water reactor, the heading “Pressurized Water Reactor Design” would be incomplete and misleading, since it does not include the concept of operation.<\/li>\n<\/ul>\n
Heading Level<\/h3>\n
- \n
- Use a different style for each level of heading: main headings within the text (not the same as the title), second level, third level, etc. That does not always mean that you need to use different fonts; you can choose different sizes, colors, or capitalization. Apply each heading style consistently throughout the document.<\/li>\n
- Consider \u201crun-in\u201d headings (words in bold or color that actually start a sentence) only if you have a lot of heading levels. Run-in headings can help you avoid the problem of too many lower-level headings looking alike.<\/li>\n
- Use actual headings as much as possible instead of bold or italic text, for accessibility.<\/li>\n<\/ul>\n
Heading Language<\/h3>\n
- \n
- Use specific, self-explanatory language in headings. For example, instead of “Background” or “Technical Information,” use “Physics of Fiber Optics.”<\/li>\n
- When possible, omit articles from the beginning of headings to be as concise as possible. For example, “The Pressurized Water Reactor” can easily be changed to “Pressurized Water Reactors.”<\/li>\n
- Use parallel phrasing in the same level of heading, e.g., all -ing words, or all noun phrases.<\/li>\n<\/ul>\n
Heading Conventions<\/h3>\n
- \n
- Avoid stacked headings\u2014any two consecutive headings without intervening text.<\/li>\n
- Avoid a lone heading by itself without another like it in the same section. If you don’t have enough content for two headings, then you may not need a heading.<\/li>\n
- Avoid “widows and orphans” in headings, when a heading occurs at the bottom of a column or page and the text it introduces starts at the top of the next column or page. Make sure to have at least two lines of text after the heading if the heading occurs toward the end of a page, or else put the heading and its text on a new page.<\/li>\n
- Avoid pronoun reference to headings. For example, if you have a heading “Torque,” don’t begin the sentence following it with something like “This is a physics principle…..” Don’t assume that a reader will relate the pronoun “this” to the heading “Torque.”<\/li>\n
- Don’t use headings as titles for tables or figures.<\/li>\n<\/ul>\n
- \n
- \u00a0A very general guideline for reports and longer documents is to have two-three headings per regular page of text. Note that this is a guideline only, but you get the idea that you should have a few sections and headings on most pages of text in longer documents, as opposed to either a block of text, or too many sections and headings.<\/li>\n<\/ul>\n
Check out the Purdue Online Writing Lab page on APA Headings and Seriation<\/a> for details and examples of headings in APA style.<\/p>\n
<\/figure>\n Common Problems with Headings<\/h2>\n
Problems occur with headings when they are too wordy, not parallel in language, not clearly representative of their information, or not comply with general heading guidelines in some way.\u00a0 The following diagram points out some common heading problems.<\/p>\n
<\/figure>\n <\/figure>\n\ntry it<\/h3>\n
Technical writers themselves fall into errors with headings. Look at the page on Memos: Purpose and Format<\/a> in a Technical Writing text. See how many errors with headings you can identify, and explain how each error could be corrected.<\/p>\n
Compare your Answer <\/span><\/p>\n\n- \n
- The first two headings are stacked – there is no text between the main heading “Memos: Purpose and Format” and the next heading “Memos.” There is no need for the “Memos” heading; correct the stacked headings by eliminating “Memos.”<\/li>\n
- “Five Tips for Effective Business Memos” is a main heading. However, the main heading for the page indicates only two second-level headings, Purpose and Format. The “Five Tips” section does include a tip on format, but also includes a wider range of tips that deal with content and language. In this case, the main heading might be edited to be more inclusive, e.g., “Writing Effective Memos.” Then the page could logically include three second-level headings.<\/li>\n
- There’s another set of stacked headings with “Five Tips” and “Audience Orientation.” Insert some text here.<\/li>\n
- The headings that come after “Five Tips” are visually at the same level as “Five Tips,” in the same size and bold blue type. Yet these headings (“Audience Orientation,” “Professional Formal Tone,” etc.) should be third-level headings, since they offer specific tips.\u00a0 Correct them by differentiating them in size and color.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n
<\/p>\n\n\t\t\t
\n\t\t\t Candela Citations<\/h3>\n\t\t\t\t\t
\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tCC licensed content, Original<\/div>- Headings, adapted from Open Technical Communication; attributions below. Authored by<\/strong>: Susan Oaks. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>CC licensed content, Shared previously<\/div>
- Headings (pages 1-4). Authored by<\/strong>: David McMurrey & Cassandra Race. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/ZEQwxjK8lbSPHW\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- Page Design (page 2 of 6). Authored by<\/strong>: David McMurrey and Jonathan Arnett. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/GZgMx1yw3kRhzL\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- image of file folders with tabs for headings. Authored by<\/strong>: Ulrike Mai . Provided by<\/strong>: Pixabay. Located at<\/strong>: https:\/\/pixabay.com\/photos\/hanging-files-filing-cabinet-1920437\/<\/a>. License<\/strong>: CC0: No Rights Reserved<\/a><\/em><\/li><\/ul><\/div>\n\t\t\t\t\t\t <\/div>\n\t\t\t\t\t <\/div>\n\t\t\t <\/section>","protected":false},"author":81366,"menu_order":3,"template":"","meta":{"_candela_citation":"[{\"type\":\"original\",\"description\":\"Headings, adapted from Open Technical Communication; attributions below\",\"author\":\"Susan Oaks\",\"organization\":\"Empire State College, SUNY\",\"url\":\"\",\"project\":\"Technical Writing\",\"license\":\"cc-by-nc\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"Headings (pages 1-4)\",\"author\":\"David McMurrey & Cassandra Race\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/ZEQwxjK8lbSPHW\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"Page Design (page 2 of 6)\",\"author\":\"David McMurrey and Jonathan Arnett\",\"organization\":\"Kennesaw State University\",\"url\":\"https:\/\/softchalkcloud.com\/lesson\/serve\/GZgMx1yw3kRhzL\/html\",\"project\":\"Open Technical Communication\",\"license\":\"cc-by\",\"license_terms\":\"\"},{\"type\":\"cc\",\"description\":\"image of file folders with tabs for headings\",\"author\":\"Ulrike Mai \",\"organization\":\"Pixabay\",\"url\":\"https:\/\/pixabay.com\/photos\/hanging-files-filing-cabinet-1920437\/\",\"project\":\"\",\"license\":\"cc0\",\"license_terms\":\"\"}]","CANDELA_OUTCOMES_GUID":"","pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-202","chapter","type-chapter","status-publish","hentry"],"part":193,"_links":{"self":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/users\/81366"}],"version-history":[{"count":14,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202\/revisions"}],"predecessor-version":[{"id":1678,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202\/revisions\/1678"}],"part":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/parts\/193"}],"metadata":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapters\/202\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/media?parent=202"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/pressbooks\/v2\/chapter-type?post=202"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/contributor?post=202"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/courses.lumenlearning.com\/suny-esc-technicalwriting\/wp-json\/wp\/v2\/license?post=202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Page Design (page 2 of 6). Authored by<\/strong>: David McMurrey and Jonathan Arnett. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/GZgMx1yw3kRhzL\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- Headings (pages 1-4). Authored by<\/strong>: David McMurrey & Cassandra Race. Provided by<\/strong>: Kennesaw State University. Located at<\/strong>: https:\/\/softchalkcloud.com\/lesson\/serve\/ZEQwxjK8lbSPHW\/html<\/a>. Project<\/strong>: Open Technical Communication. License<\/strong>: CC BY: Attribution<\/a><\/em><\/li>
- Headings, adapted from Open Technical Communication; attributions below. Authored by<\/strong>: Susan Oaks. Provided by<\/strong>: Empire State College, SUNY. Project<\/strong>: Technical Writing. License<\/strong>: CC BY-NC: Attribution-NonCommercial<\/a><\/em><\/li><\/ul>
- \u00a0A very general guideline for reports and longer documents is to have two-three headings per regular page of text. Note that this is a guideline only, but you get the idea that you should have a few sections and headings on most pages of text in longer documents, as opposed to either a block of text, or too many sections and headings.<\/li>\n<\/ul>\n
- \u00a0A very general guideline for reports and longer documents is to have two-three headings per regular page of text. Note that this is a guideline only, but you get the idea that you should have a few sections and headings on most pages of text in longer documents, as opposed to either a block of text, or too many sections and headings.<\/li>\r\n<\/ul>\r\nCheck out the Purdue Online Writing Lab page on APA Headings and Seriation<\/a> for details and examples of headings in APA style.\r\n