Edits, moved voice and tone to writing, from style guidelines

Author: JuliaMongo

source/style-guide/style/callouts.txt

@@ -6,9 +6,8 @@ Callouts and Admonitions
 
 .. default-domain:: mongodb
 
-Callouts or admonitions emphasize important or
-helpful information. Use callouts sparingly to avoid clutter on
-the page and to preserve visual impact. 
+Callouts or admonitions emphasize important or helpful information. Use
+callouts sparingly to avoid clutter on the page and to preserve visual impact. 
 
 Callout Types
 -------------
@@ -79,12 +78,12 @@ When creating callouts, use the following guidelines:
    attempt to create callouts using boldface, headings, or custom
    :abbr:`CSS (Cascading Style Sheets)`.
 
-- Don't stack multiple admonitions directly after one another, as these
-  can be distracting for users. To avoid stacking admonitions, group
-  supplemental information from admonitions into a dedicated section.
+- Don't stack multiple callouts directly after one another, as these can
+  distract users. To avoid stacking callouts, group supplemental information
+  from callouts into a dedicated section.
 
-- Don't use admonitions in tables and option lists, if possible, because
-  admonitions reduce scannability of tables and options lists.
+- Don't use callouts in tables and option lists, if possible, because
+  callouts reduce the scannability of tables and options lists.
 
 -  Avoid nesting callouts inside tables and other elements.
 
@@ -93,11 +92,9 @@ When creating callouts, use the following guidelines:
 -  Place a callout as close as possible to the information that it
    emphasizes or clarifies.
 
--  Avoid "stack" callouts of the same type. For example, avoid adding
+-  Avoid stacking callouts of the same type. For example, avoid adding
    one labeled note directly after another labeled note. Instead, use
    separate paragraphs or an unordered list within a single callout.
-   You can have callouts of different types follow one
-   another, if necessary, but if possible, avoid such situations also.
 
 The following callouts might appear in existing documentation but are
 deprecated. Don't use these callouts in new content:

source/style-guide/style/cloud-account-info.txt

@@ -6,6 +6,12 @@ API Placeholders
 
 .. default-domain:: mongodb
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 1
+   :class: singlecol
+
 When users learn how to use our API, they might copy the code and try
 to use it as given. 
 

source/style-guide/style/code-examples.txt

@@ -4,6 +4,12 @@
 Code Examples
 =============
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 1
+   :class: singlecol
+
 Use the following guidelines when creating blocks of code as input
 or output examples:
 

source/style-guide/style/index.txt

@@ -47,4 +47,3 @@ instructions for applying style conventions.
    /style-guide/style/titles-and-headings
    /style-guide/style/urls
    /style-guide/style/version
-   /style-guide/style/voice-and-tone

source/style-guide/style/ip-addresses.txt

@@ -6,6 +6,12 @@ IP Addresses
 
 .. default-domain:: mongodb
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 1
+   :class: singlecol
+
 An *IP address* uses a sequence of numbers to uniquely identify a
 particular computer on the Internet.
 

source/style-guide/style/links-and-cross-references.txt

@@ -4,12 +4,6 @@
 Links and Cross-References
 ==========================
 
-.. contents:: On this page
-   :local:
-   :backlinks: none
-   :depth: 2
-   :class: singlecol
-
 .. default-domain:: mongodb
 
 Documentation writers use links to direct users to related material
@@ -75,25 +69,25 @@ about MongoDB concepts can click through and explore the linked content.
 Avoid Inline References in Tutorials
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- Avoid adding inline textual references in tutorials or stepped procedures. 
+Avoid adding inline textual references in tutorials or stepped procedures. 
 
-  If users follow inline references while in the middle of a procedure,
-  they might have difficulty navigating back and reorienting themselves
-  with their current step.
+If users follow inline references while in the middle of a procedure,
+they might have difficulty navigating back and reorienting themselves
+with their current step.
 
-  Inline textual references may be appropriate for more reference-heavy pages.
+Inline textual references may be appropriate for more reference-heavy pages.
 
 Minimize Repeated Links
 ~~~~~~~~~~~~~~~~~~~~~~~
 
 - Don't link to the same target multiple times in the same section.
 
-  You may link to the same target more than once on the same page, but
+  You may link to the same target multiple times on the same page, but
   think carefully about whether it's absolutely necessary. For example,
-  if a page is long and contains many sections, then it might be helpful
-  to link to a target once or twice from this page to help users who
-  navigate to a section far down on a page and may miss the initial
-  reference at the top of the page.
+  if a page is particularly long and contains many sections, then it might
+  be helpful to link to a target an additional time or two. Users may
+  immediately navigate to a section far down on a page and miss the initial
+  reference.
 
 - If you add repeated links, use the same style for each link.
   Consider whether a plaintext link or a monospace link is appropriate.

source/style-guide/style/placeholder-variable-text.txt

@@ -6,6 +6,12 @@ Placeholder or Variable Text
 
 .. default-domain:: mongodb
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 1
+   :class: singlecol
+
 Use placeholder text for a value when you:
 
 - Don't know its specific value

source/style-guide/writing/index.txt

@@ -23,6 +23,7 @@ and consistent, and that helps users accomplish their goals.
    /style-guide/writing/use-gender-neutral-pronouns
    /style-guide/writing/use-positive-statements
    /style-guide/writing/use-correct-punctuation
+   /style-guide/style/voice-and-tone
    /style-guide/writing/use-interjections-with-care
    /style-guide/writing/write-for-accessibility
    /style-guide/terminology/terms-for-global-audience

source/style-guide/writing/use-active-voice.txt

@@ -4,6 +4,12 @@
 Use Active Voice
 ================
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
 .. default-domain:: mongodb
 
 .. _why-active-voice:

source/style-guide/writing/use-positive-statements.txt

@@ -4,6 +4,12 @@
 Use Positive Statements
 =======================
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 1
+   :class: singlecol
+
 Positive statements are easier to understand than negative statements
 and are typically shorter.
 

source/style-guide/writing/use-present-tense.txt

@@ -4,6 +4,12 @@
 Use Present Tense
 =================
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
 .. default-domain:: mongodb
 
 Users read content to learn how to perform tasks or to gather

source/style-guide/writing/write-to-the-user.txt

@@ -8,6 +8,14 @@ Use Second Person and Imperative Mood
 
 .. default-domain:: mongodb
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
+.. default-domain:: mongodb
+
 Write to the User
 -----------------