SA review comments

Author: lindseymoore

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

@@ -50,14 +50,18 @@ Each of the following four subsections describe one of the above principles.
 Title Length
 ~~~~~~~~~~~~
 
-Titles should be between 30-60 character long. Pages with titles longer than 60 characters
+Titles should be between 30-60 characters long. Pages with titles longer than 60 characters
 are typically truncated by search engines. A too short title does not convey enough information
 to the search engine, so a page with a too short title might be recommended less by search
 engines. Search engines might also create a longer page title for pages with too short titles.
 
-When considering title length, keep in mind that the product name and version number
-count towards title length. This can add around 6-20 characters to the title, depending
-on the length of the product name. 
+When considering title length, keep in mind that the product name, version 
+number, and "MongoDB Docs" are automatically appended when the title is passed 
+to a search engine. For example, a v8.0 Server Manual page titled 
+"Install MongoDB", the title is 15 characters long. The full title passed to search
+engines ("Install MongoDB - Database Manual v8.0 - MongoDB Docs") is 53 characters long.
+The appended additions to the title can add around 18-35 
+characters to the title, depending on the length of the product name. 
 
 Standardization
 ~~~~~~~~~~~~~~~
@@ -140,6 +144,8 @@ words:
    To learn more about the principles of headline-style capitalization,
    read `section 8.159 <https://www.chicagomanualofstyle.org/book/ed17/part2/ch08/psec159.html>`__ of the *Chicago Manual of Style*.
 
+.. _general-title-guidance:
+
 Guidelines for Titles and Headings
 ----------------------------------
 
@@ -148,6 +154,8 @@ titles and headings. Special considerations for stand-alone articles, product
 guides, and tables, figures, and examples can be found in the Product Guides and
 Tables, Figures, and Headings subsections. 
 
+.. _title-grammar:
+
 Grammatical Structure for Different Page Types
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -166,59 +174,59 @@ specific types of content:
      * - Conceptual
        - Any grammatical structure that's appropriate, except a verb,
          gerund, or infinitive
-       - Linux distributions
+       - Linux Distributions
 
-         Best practices for backing up your data
+         Best Practices for Backing Up Your Data
        - Core concepts
 
-         How monitoring works
+         How Monitoring Works
 
-         Limitations of detaching from MongoDB networks
+         Limitations of Detaching from MongoDB Networks
 
      * - Tutorial or high-level process
        - An imperative verb
 
          .. note::
             For specific guidelines for headings within tasks, see
             :ref:`tasks`.
-       - Identify network interfaces on Linux
+       - Identify Network Interfaces on Linux
 
-         Prepare data disks on servers running Windows
+         Prepare Data Disks on Servers Running Windows
 
-         Set up Mobile Sync for Webmail
-       - Sign up for a MongoDB Atlas account
+         Set Up Mobile Sync for Webmail
+       - Sign Up for a MongoDB Atlas Account
 
      * - Reference
        - A plural noun or a noun phrase
-       - Permissions matrix for Cloud Networks
+       - Permissions Matrix for Cloud Networks
 
-         MongoDB Auto Scale glossary
-       - Environment variables for the nova and supernova clients
+         MongoDB Auto Scale Glossary
+       - Environment Variables for the Nova and Supernova Clients
 
-         Restore operations
+         Restore Operations
 
-         cURL command summary
+         cURL Command Summary
 
      * - Troubleshooting
        - A grammatical structure that's appropriate for the type of
          content (a troubleshooting topic can contain task, tutorial,
          concept, or reference information)
-       - Troubleshoot alarms
+       - Troubleshoot Alarms
 
-         Service troubleshooting on Linux
+         Service Troubleshooting on Linux
        - Troubleshooting
 
      * - FAQ
        - A descriptive noun or noun phrase, followed by *FAQ*
        - MongoDB Cloud Billing FAQ
 
-         Scheduled images FAQ
+         Scheduled Images FAQ
        - Not applicable
 
 General Style and Structure
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The following guidelines apply to all titles and headings; 
+The following guidelines apply to all titles and headings:
 
 - Create succinct, meaningful, descriptive titles and headings, and
   place the most important words first.