Merge pull request #154 from norareidy/fix-inconsistencies

Inconsistent capitalization info and typos

Author: Chris Cho

source/style-guide/error-message-guidelines.txt

@@ -6,7 +6,7 @@ Error Message Guidelines
 
 .. default-domain:: mongodb
 
-Developers often ask an Technical Writer to edit error messages
+Developers often ask a technical writer to edit error messages
 that they have written.
 
 When you edit error messages, use the writing guidelines in this Style

source/style-guide/markup/inline.txt

@@ -31,7 +31,7 @@ To learn more about when to use these roles, see the style guide section on
 
      **bold**
 
-- To *emphasize* or *italicize* text, use two asterisks on both sides
+- To *emphasize* or *italicize* text, use one asterisk on both sides
   of the text.
 
   .. code-block:: rst

source/style-guide/quickstart.txt

@@ -86,12 +86,11 @@ the following ones to help you boost the effectiveness of your writing.
      - :ref:`use-correct-punctuation`
 
        :ref:`punctuation`
-   * - **Use sentence-style capitalization for all titles and
+   * - **Use AP headline-style capitalization for all titles and
        headings**.
 
-       In sentence-style capitalization, you capitalize only the first
-       word of the title or heading, plus any proper terms and terms
-       that are always capitalized, such as some abbreviations.
+       To meet AP headline-style (or AP title case) capitalization requirements, 
+       refer to the guidelines in the :ref:`titles-and-headings` guide.
      - :ref:`titles-and-headings`
    * - **Write clear and consistent code examples**.
 

source/style-guide/screenshots/diagram-guidelines.txt

@@ -101,7 +101,7 @@ Text Formatting
 -  **Font**: Set the font to **Helvetica**.
 
 -  **Titles:** Title must be **bolded**, aligned **left**, and be at
-   least **24px** in size. Use sentence-style capitalization.
+   least **24px** in size. Use headline-style capitalization.
 
 Objects
 ~~~~~~~

source/style-guide/style/punctuation.txt

@@ -138,7 +138,7 @@ in the *Chicago Manual of Style*.
        Unlike the other alarms in this list you set the network check
        alarm variable upon network check creation.
 
-       To learn more, see Upgrading Ops Manager.
+       To learn more see Upgrading Ops Manager.
 
    * - Don't use a comma between the verbs in a compound predicate.
      - These open-source Python clients run on Linux or Mac OS X

source/style-guide/style/tables.txt

@@ -49,8 +49,8 @@ within tasks, procedures, and tutorials don't require titles.
 
 When creating table titles, use the following guidelines:
 
-- Use sentence-style capitalization for table titles. However, for
-  words that are always uppercase or always lowercase, match that case.
+- Use headline-style capitalization for table titles. To learn more, see 
+  :ref:`titles-and-headings`.
 - Don't start a table title with an article (*a*, *an*, *the*).
 - Don't end a table title with a period or colon.
 - Place the title above the table, not below it, and format it in 

source/style-guide/style/titles-and-headings.txt

@@ -16,7 +16,7 @@ documentation.
 Capitalization
 --------------
 
-- Use *headline-style* capitalization for most titles and headings,
+- Use *AP headline-style* capitalization for most titles and headings,
   including article, chapter, table, figure, and example titles, as
   well as section and procedure headings.
 
@@ -28,7 +28,7 @@ Capitalization
 Guidelines for Headline-Style Capitalization
 --------------------------------------------
 
-Title-style capitalization uses initial uppercase letters for the
+AP headline-style capitalization uses initial uppercase letters for the
 first, last, and all the significant words in the title.
 
 Capitalize all words in the title except for the following types of

source/style-guide/terminology/general-term-guidelines/use-consistent-terms.txt

@@ -45,10 +45,9 @@ consistently throughout the documentation.
    same document can be confusing to users and translators, so avoid
    it when possible.
 
--  Avoid neologisms. Examples of neologisms -- or
-   newly invented words -- are *marketecture* or *edutainment*. Most
-   such words are specific to a single business culture and aren't
-   understood in other cultures.
+-  Avoid neologisms. Examples of neologisms (newly invented words) 
+   include *marketecture* or *edutainment*. Most of these words are specific 
+   to a single business culture and aren't understood in other cultures.
 
 -  Standardize words and spelling across a documentation set.