Tips for Creating an EffectiveTOC

3 4

Headings are the real secret in creating a helpful table of contents. If you've written clear, understandable headings, your readers will know where to turn for the information they want. The next consideration is the way in which you format those headings—if you don't use styles Word recognizes, the program won't collect the headings the way you want it to. To create the TOC you want, keep these guidelines in mind:

  • Use Word's built-in heading styles—or create your custom styles based on them. When you're working in Outline view or working with master documents, it's important that you use Word's built-in headings styles—Heading 1, Heading 2, or Heading 3. Additionally, you can use the various outline levels—1 through 9—but any other style won't be included in the table of contents Word generates for you.
  • Make your headings clear and concise. The best headings are short—between 4 and 10 words—and communicate the subject clearly. The headings for your document will vary, of course, depending on content, but if your objective is to help readers find what they want quickly, you'll be closer to meeting your goal if you keep your headings short, sweet, and smart.
  • Avoid confusing headings. If the tone of your document is conversationally hip, you might be tempted to throw in little humorous sayings or quips as headings throughout your text. As a wise editor once asked, "Would readers understand what this heading means if they opened the book at this page?" If helping readers is your main goal, avoid phrases that might confuse them.

Note


You can literally include any text in your document as part of the TOC by selecting the entries manually. For more information on manual table of contents entries, see "Adding TOC Entries Manually".



Microsoft Word Version 2002 Inside Out
Microsoft Word Version 2002 Inside Out (Inside Out (Microsoft))
ISBN: 0735612781
EAN: 2147483647
Year: 2005
Pages: 337

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net