trivial: fix build warnings

Author: kay-kim

source/includes/extracts-command-field.yaml

@@ -22,7 +22,7 @@ content: |
   The ``comment`` field is present if a comment was passed to the operation.
   
   The following example output contains the command object for a
-  :doc:`find </reference/method/db.collection.find/#db.collection.find>`
+  :dbcommand:`find`
   operation on a collection named ``items`` in a database
   named ``test``:
   
@@ -37,7 +37,7 @@ content: |
      }
   
   The following example output contains the command object for a
-  :doc:`getMore </reference/command/getMore>` operation generated by
+  :dbcommand:`getMore` operation generated by
   a command with cursor id ``80336119321`` on a collection named
   ``items`` in a database named ``test``:
   
@@ -62,4 +62,4 @@ source:
   ref: _command-field
 replacement:
   truncThreshold: "50 kilobytes"
-...
+...

source/reference/command/replSetResizeOplog.txt

@@ -86,4 +86,4 @@ The above command returns:
 
    Reducing the size of the oplog in a node removes data from it. This
    may cause replica members syncing with that node to become stale.
-   To resync those members, see :ref:`resync-replica-set-member`.
+   To resync those members, see :doc:`/tutorial/resync-replica-set-member`.

source/reference/method/db.collection.find.txt

@@ -129,7 +129,7 @@ because its ``qty`` value is of type ``object``.
 
 .. note::
    To enforce data types in a collection, use 
-   :doc:`/core/document-validation`.
+   :doc:`/core/schema-validation`.
 
 Examples
 --------

source/release-notes/3.6.txt

@@ -321,7 +321,7 @@ Retryable Writes
      :dbcommand:`setFeatureCompatibilityVersion`.
 
 Starting in MongoDB 3.6, :ref:`certain acknowledged write
-operations <retryable-ops>` on replica sets and sharded clusters are
+operations <retryable-write-ops>` on replica sets and sharded clusters are
 "retryable" to provide handling of transient network errors or replica
 set elections.
 

source/tutorial/change-streams-example.txt

@@ -12,7 +12,7 @@ Change Stream Examples
 
 .. important::
    Change streams are available for replica sets or sharded clusters with replica set
-   shards. You cannot open a change stream against a standalone :program:`mongod`. 
+   shards. You cannot open a change stream against a standalone :program:`mongod`.
    For a sharded cluster, you must issue the open change stream operation against
    the :program:`mongos`.
 
@@ -22,9 +22,6 @@ Change Stream Examples
 
    -  :ref:`WiredTiger <storage-wiredtiger>` storage engine (can be :ref:`encrypted <encrypted-storage-engine>`)
 
-
-
-
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -36,57 +33,53 @@ Change Stream Examples
    tabs:
      - id: python
        content: |
-         
+
          The examples below assume that you have `connected to a MongoDB replica set and have accessed a database
          <http://api.mongodb.com/python/current/tutorial.html?_ga=2.166792574.1325858930.1510605946-1663796716.1426889906#making-a-connection-with-mongoclient/>`_
          that contains an ``inventory`` collection.
 
-     
      - id: java-sync
        content: |
          The examples below assume that you have `connected to a MongoDB replica set and have accessed a database
          <http://mongodb.github.io/mongo-java-driver/3.6/driver/tutorials/databases-collections/>`_
          that contains an ``inventory`` collection.
-  
+
      - id: csharp
        content: |
           The examples below assume that you have `connected to a MongoDB replica set and have accessed a database
-          <http://mongodb.github.io/mongo-csharp-driver/2.4/getting_started/quick_tour/#make-a-connection/>`_  
+          <http://mongodb.github.io/mongo-csharp-driver/2.4/getting_started/quick_tour/#make-a-connection/>`_
           that contains an ``inventory`` collection.
-  
+
      - id: c
        content: |
          The examples below assume that you have `connected to a MongoDB replica set and have accessed a database
          <http://mongoc.org/libmongoc/current/tutorial.html#making-a-connection/>`_
          that contains an ``inventory`` collection.
-  
-    
 
 Open A Change Stream
 --------------------
-       
+
 This example opens a change stream against a replica set. The change stream is bound to a collection and
 change stream documents are iterated with a cursor. This cursor remains open until it is explicitly closed,
 as long as a connection to the MongoDB deployment remains open *and* the collection exists.
 
-
 .. tabs-drivers::
 
    tabs:
      - id: python
        content: |
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/test_examples.py
             :language: python
             :dedent: 8
-            :start-after: Start Changestream Example 1 
+            :start-after: Start Changestream Example 1
             :end-before: End Changestream Example 1
 
      - id: java-sync
        content: |
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/DocumentationSamples.java
             :language: java
             :dedent: 8
@@ -101,11 +94,11 @@ as long as a connection to the MongoDB deployment remains open *and* the collect
             :dedent: 12
             :start-after: Start Changestream Example 1
             :end-before: End Changestream Example 1
-            
+
      - id: c
        content: |
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/test-mongoc-sample-commands.c
             :language: c
             :dedent: 0
@@ -129,44 +122,44 @@ Lookup Full Document for Update Operations
    tabs:
      - id: python
        content: |
-         By default, change streams only return the delta of fields during the update operation. 
+         By default, change streams only return the delta of fields during the update operation.
          To return the most current majority-committed version of the updated
          document, pass ``full_document='updateLookup'`` to the
-         :method:`db.collection.watch()` method. 
-   
+         :method:`db.collection.watch()` method.
+
      - id: java-sync
        content: |
-         By default, change streams only return the delta of fields during the update operation. 
+         By default, change streams only return the delta of fields during the update operation.
          To return the most current majority-committed version of the updated
          document, pass ``FullDocument.UPDATE_LOOKUP``  to the
-         :method:`db.collection.watch.fullDocument()` method. 
-         
+         :method:`db.collection.watch.fullDocument()` method.
+
      - id: c
        content: |
-         By default, change streams only return the delta of fields during the update operation. 
+         By default, change streams only return the delta of fields during the update operation.
          To return the most current majority-committed version of the updated
          document, pass the ``"fullDocument"`` option with the ``"updateLookup"`` value to the
-         :method:`mongoc_collection_watch` method. 
-      
+         :method:`mongoc_collection_watch` method.
+
      - id: csharp
        content: |
-         By default, change streams only return the delta of fields during the update operation. 
+         By default, change streams only return the delta of fields during the update operation.
          To return the most current majority-committed version of the updated
          document, pass ``"FullDocument = ChangeStreamFullDocumentOption.UpdateLookup"`` to the
-         :method:`collection.Watch()` method. 
+         :method:`collection.Watch()` method.
 
 
 If there are one or more majority-committed operations that modified the
 updated document *after* the update operation but *before* the lookup, the
 full document returned may differ significantly from the document at the time
 of the update operation.
- 
-However, the deltas included in the change stream document always 
-correctly describe the watched 
+
+However, the deltas included in the change stream document always
+correctly describe the watched
 collection changes that applied to that change stream event.
 
 Iterate the change stream ``cursor`` to retrieve the change stream
-documents in order. In the example below, all update operations notifications 
+documents in order. In the example below, all update operations notifications
 include a ``fullDocument``
 field that represents the *current* version of the document affected by the
 update operation.
@@ -177,17 +170,17 @@ update operation.
      - id: python
        content: |
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/test_examples.py
             :language: python
             :dedent: 8
-            :start-after: Start Changestream Example 2 
+            :start-after: Start Changestream Example 2
             :end-before: End Changestream Example 2
 
      - id: java-sync
        content: |
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/DocumentationSamples.java
             :language: java
             :dedent: 8
@@ -197,17 +190,17 @@ update operation.
      - id: csharp
        content: |
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/ChangeStreamExamples.cs
             :language: C#
             :dedent: 12
             :start-after: Start Changestream Example 2
             :end-before: End Changestream Example 2
-            
+
      - id: c
        content: |
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/test-mongoc-sample-commands.c
             :language: C
             :dedent: 0
@@ -254,7 +247,6 @@ more of the following pipeline stages when configuring the change stream:
 
             MongoCursor<Document> cursor = collection.watch(pipeline).iterator();
 
-
 .. tabs-drivers::
 
    tabs:
@@ -271,8 +263,7 @@ more of the following pipeline stages when configuring the change stream:
 See :ref:`change-stream-output` for more information on the change stream
 response document format.
 
-
-.. change-stream-resume::
+.. _change-stream-resume:
 
 Resume a Change Stream
 ----------------------
@@ -291,13 +282,13 @@ notification after a specific notification.
          token. Passing the ``resumeToken`` to the ``resumeAfter`` modifier directs
          the change stream to attempt to resume notifications starting at the
          operation specified in the resume token.
-         
+
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/test_examples.py
             :language: python
             :dedent: 8
-            :start-after: Start Changestream Example 3 
+            :start-after: Start Changestream Example 3
             :end-before: End Changestream Example 3
 
      - id: java-sync
@@ -306,9 +297,9 @@ notification after a specific notification.
          token. Passing the ``resumeToken`` to the ``resumeAfter()`` method directs
          the change stream to attempt to resume notifications starting at the
          operation specified in the resume token.
-         
+
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/DocumentationSamples.java
             :language: java
             :dedent: 8
@@ -318,37 +309,35 @@ notification after a specific notification.
      - id: csharp
        content: |
          In the example below, the ``resumeToken`` is retrieved from the last change stream document
-         and passed to the ``Watch()`` method as an option. Passing the ``resumeToken`` 
+         and passed to the ``Watch()`` method as an option. Passing the ``resumeToken``
          to the ``Watch()`` method directs
          the change stream to attempt to resume notifications starting at the
          operation specified in the resume token.
-         
+
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/ChangeStreamExamples.cs
             :language: C#
             :dedent: 12
             :start-after: Start Changestream Example 3
             :end-before: End Changestream Example 3
-            
+
      - id: c
        content: |
          In the example below, the ``resumeAfter`` option is appended to the stream options
          to recreate the stream after it has been destroyed. Passing the ``_id` to
          the change stream attempts to resume notifications starting at the
          operation specified.
-         
+
          .. class:: copyable-code
-         
+
          .. literalinclude:: /driver-examples/test-mongoc-sample-commands.c
             :language: C
             :dedent: 0
             :start-after: Start Changestream Example 3
             :end-before: End Changestream Example 3
 
 
-
-
 As long as that operation has not rolled off the :term:`oplog`, the
 change stream can successfully resume notifications.