grammar fixes

Author: Chris Cho

source/style-guide/markup/directives/sharedinclude.txt

@@ -7,7 +7,7 @@ Shared Include
 The ``sharedinclude`` directive lets you source content from a file located in
 the MongoDB internal `docs-shared <https://github.com/10gen/docs-shared>`__
 repository. Use this directive when you need to keep the same content in sync
-for multiple sets of documentation or multiple branches of a documentation set.
+for multiple sets of documentation or branches of a documentation set.
 
 This page uses the following terms:
 
@@ -20,17 +20,17 @@ Sourcing file
   directive to pull content from an external file.
 
 Placeholder
-  A variable that indicates text that the sourcing file must provide a
-  replacement for. These variables are represented by the placeholder name
-  surrounded by the ``|`` (pipe) character. The variables are used in
-  external files.
+  A variable that identifies where replacement content should be inserted.
+  These variables are represented as a name surrounded by the ``|`` (pipe)
+  character. Add them in the external file and define the replacement content
+  in the sourcing file.
 
 .. tip::
 
-   The ``sharedinclude`` directive is an extension of the ``include`` directive.
+   The ``sharedinclude`` directive extends the ``include`` directive.
    While the ``include`` directive allows you to source content from the
    branch of the repository in which it is used, the ``sharedinclude``
-   directive is hardcoded to reference external files from the
+   directive is hard-coded to reference external files from the
    `10gen/docs-shared <https://github.com/10gen/docs-shared/>`__
    private GitHub repository.
 
@@ -41,7 +41,7 @@ Setup
 You must ensure the ``sharedinclude_root`` setting in the documentation
 repository's ``snooty.toml`` configuration file is set to the shared
 content repository URL. This URL must point to the unprocessed version of the
-files, currently served from the ``raw.githubusercontent.com`` domain.
+files currently served from the ``raw.githubusercontent.com`` domain.
 
 For example, if the external files that your docs repository file references
 is on the ``main`` branch of ``docs-shared``, your docs repository
@@ -58,23 +58,23 @@ configuring this setting.
 Syntax
 ------
 
-To include content from an external file, add the ``sharedinclude`` directive
-to the sourcing file. Specify the path of the external file relative to the
+Add the ``sharedinclude`` directive to the sourcing file to include content
+from the external file.  Specify the path of the external file relative to the
 ``docs-shared`` base directory, omitting the leading slash.
 
 For example, if the file path from the root of the ``docs-shared`` repository
-is ``drivers/compatibility-tables/c.rst``, the {+rst-abbrev+} in the sourcing file
-should include the following code:
+is ``drivers/compatibility-tables/c.rst``, the {+rst-abbrev+} in the sourcing
+file should include the following code:
 
 .. code-block:: rst
    :caption: sourcing_file.txt in a documentation repository
    :copyable: false
 
    .. _sharedinclude:: drivers/compatibility-tables/c.rst
 
-The external file can include replacement variables in the form of
-``|variable-name|``. This enables the sourcing file to customize segments
-of the page.
+The external file includes replacement variables in the form of
+``|variable-name|``. You can define the replacement values in sourcing files
+to customize segments of the page.
 
 For example, suppose the ``docs-shared`` file ``language.rst`` contained the
 following content with a replacement variable called ``|driver-name|``:
@@ -118,15 +118,15 @@ Placeholders in Inline Context
 
 An **inline context** describes the positioning of placeholders as adjacent to
 other paragraph text. If the placeholder is in an inline context, you can
-replace it with markup elements including the following types:
+replace it with markup elements, including the following types:
 
 - Unformatted text
 - Formatted text such as ``monospace``, **emphasis**, or *italic*
 - Links
 
 You cannot replace variable placeholders in inline contexts with elements
 such as lists, code blocks, includes, and headers. If you need to
-source these elements from a ``sharedinclude``, make sure the placeholders
+source these elements from a ``sharedinclude``, ensure the placeholders
 are in a block context as described in the next section.
 
 For example, suppose you want to source content from an external file, located
@@ -167,24 +167,24 @@ Placeholders in Block Context
 `````````````````````````````
 
 A **block context** describes the positioning of placeholders as
-separated from paragraph text by line breaks. You can replace variable
-placeholders in a block context with most inline or block {+rst-abbrev+}
-elements, including the following types:
+separated from paragraph text by line breaks. You can replace placeholders in
+a block context with most inline or block {+rst-abbrev+} elements, including
+the following types:
 
 - Titles
 - Code blocks
 - Anchors
 - Admonitions
 
-For example, suppose you want to source content from an external file, located
+For example, suppose you want to source content from an external file located
 at ``dbx/fundamentals/agg-operators.rst`` in the ``docs-shared`` repository,
 which contains the following content:
 
 .. code-block:: rst
    :caption: dbx/fundamentals/agg-operators.rst external file in docs_shared
    :copyable: false
 
-   The next section demonstrates how to use aggregation operators to build
+   The following section demonstrates how to use aggregation operators to build
    an aggregation pipeline.
 
    |aggregation-operators-example|
@@ -219,7 +219,7 @@ The published page renders as if the sourcing file contained the following {+rst
 .. code-block:: rst
    :copyable: false
 
-   The next section demonstrates how to use aggregation operators to build
+   The following section demonstrates how to use aggregation operators to build
    an aggregation pipeline.
 
    .. _expression-operators-example: