DOCSP-15360, DOCSP-15407 foreport address build errors part2

Author: andf-mongodb

source/core/gridfs.txt

@@ -281,10 +281,10 @@ chunks, as demonstrated in the following example:
 
    db.fs.chunks.find( { files_id: myFileID } ).sort( { n: 1 } )
 
-:driver:`Drivers </>` that conform to the `GridFS
-specification`_ will automatically ensure that this index exists before
-read and write operations. See the relevant driver documentation for the
-specific behavior of your GridFS application.
+:driver:`Drivers </>` that conform to the :spec:`GridFS specification
+</gridfs/gridfs-spec.rst>`  will automatically ensure that this index
+exists before read and write operations. See the relevant driver
+documentation for the specific behavior of your GridFS application.
 
 If this index does not exist, you can issue the following operation to
 create it using the :binary:`~bin.mongo` shell:

source/includes/extracts-server-status-projection-base.yaml

@@ -145,7 +145,7 @@ content: |
       :serverstatus:`opcountersRepl` metrics as 64-bit integers (i.e.
       NumberLong) instead of 32-bit integers (i.e. NumberInt).
 
-    - Includes :serverstatus:`trafficRecording` metrics in its output.
+    - Includes ``trafficRecording`` metrics in its output.
 
     - Added new document count (``countDocs``) metrics in
       :serverstatus:`shardingStatistics`.

source/reference/built-in-roles.txt

@@ -524,7 +524,7 @@ Cluster Administration Roles
           <<database>.system.namespaces>` collections.
 
 
-      * - | :data:`system.replset <<database>.system.replset>`,
+      * - | :data:`system.replset <local.system.replset>`,
           | :data:`system.profile <<database>.system.profile>`,
 
         - :authaction:`find`
@@ -764,9 +764,10 @@ All-Database Roles
    - :authaction:`listDatabases`
 
    The role also provides the following privilege actions on the
-   :data:`system.users` and :data:`system.roles`
-   collections on the ``admin`` database, and on legacy
-   ``system.users`` collections from versions of MongoDB prior to 2.6:
+   :data:`system.users <admin.system.users>` and
+   :data:`system.roles <admin.system.roles>` collections on the
+   ``admin`` database, and on legacy ``system.users`` collections from
+   versions of MongoDB prior to 2.6:
 
    - :authaction:`collStats`
    - :authaction:`dbHash`

source/reference/command/buildInfo.txt

@@ -48,6 +48,7 @@ buildInfo
            "bits" : <num>,
            "debug" : <boolean>,
            "maxBsonObjectSize" : <num>,
+           "storageEngines" : [ "<string>", "<string>", "<...>" ],
            "ok" : <num>
          }
 
@@ -74,7 +75,7 @@ These fields are stable and should provide consistent behavior.
    :binary:`~bin.mongod` instance. See :data:`~buildInfo.version` for a
    more readable version of this string.
 
-.. data:: document buildInfo.version
+.. data:: buildInfo.version
 
    A string that conveys version information about the
    :binary:`~bin.mongod` instance. If you need to present version information to
@@ -83,7 +84,7 @@ These fields are stable and should provide consistent behavior.
    This string will take the format ``<major>.<minor>.<patch>`` in the case of
    a release, but development builds may contain additional information.
 
-.. data:: document buildInfo.storageEngines
+.. data:: buildInfo.storageEngines
 
    .. versionadded:: 3.2
 

source/reference/command/collMod.txt

@@ -43,16 +43,6 @@ Definition
    For the ``<collection or view>``, specify the name of a collection
    or view in the current database.
 
-   Use the :data:`~collStats.userFlags` field in the
-   :method:`db.collection.stats()` output to check the options enabled
-   for a collection.
-
-.. Commenting out the following after DOCS-717, it does take
-   a lock but its to cover a very small metadata change.
-
-   This command obtains a write lock on the affected database
-   and will block other operations until it has completed.
-
 Options
 -------
 

source/reference/command/planCacheListFilters.txt

@@ -140,7 +140,7 @@ the following form:
 
       The array of indexes for this :term:`query shape`. To choose the
       optimal query plan, the query optimizer evaluates only the listed
-      :data:`~planCacheListFilters.hints.indexes` *and* the collection
+      :data:`~planCacheListFilters.filters.indexes` *and* the collection
       scan.
 
 .. data:: planCacheListFilters.ok

source/reference/command/replSetResizeOplog.txt

@@ -281,11 +281,11 @@ Change the Minimum Oplog Retention Period
 
 #. *Optional*. Use the :method:`db.serverStatus()` command to verify
    the current minimum oplog retention value as
-   :serverstatus:`oplogTruncation.oplogMinRetentionHours`:
+   :serverstatus:`oplogTruncation.minRetentionHours`:
 
    .. code-block:: javascript
 
-      db.getSiblingDB("admin").serverStatus().oplogTruncation.oplogMinRetentionHours
+      db.getSiblingDB("admin").serverStatus().oplogTruncation.minRetentionHours
 
    The command returns the currently configured minimum oplog retention
    period for the :binary:`~bin.mongod`. For example:

source/reference/configuration-options.txt

@@ -2915,9 +2915,9 @@ Key Management Configuration Options
 
    .. note::
 
-      Windows MongoDB deployments can use :setting:`~security.ldap.bindWithOSDefaults`
+      Windows MongoDB deployments can use :setting:`~security.ldap.bind.useOSDefaults`
       instead of :setting:`~security.ldap.bind.queryUser` and :setting:`~security.ldap.bind.queryPassword`. You cannot specify
-      both :setting:`~security.ldap.bind.queryUser` and :setting:`~security.ldap.bindWithOSDefaults` at the same time.
+      both :setting:`~security.ldap.bind.queryUser` and :setting:`~security.ldap.bind.useOSDefaults` at the same time.
 
 
 .. setting:: security.ldap.bind.queryPassword
@@ -2937,9 +2937,9 @@ Key Management Configuration Options
 
    .. note::
 
-      Windows MongoDB deployments can use :setting:`~security.ldap.bindWithOSDefaults`
+      Windows MongoDB deployments can use :setting:`~security.ldap.bind.useOSDefaults`
       instead of :setting:`~security.ldap.bind.queryPassword` and :setting:`~security.ldap.bind.queryPassword`. You cannot specify
-      both :setting:`~security.ldap.bind.queryPassword` and :setting:`~security.ldap.bindWithOSDefaults` at the same time.
+      both :setting:`~security.ldap.bind.queryPassword` and :setting:`~security.ldap.bind.useOSDefaults` at the same time.
 
 
 .. setting:: security.ldap.bind.useOSDefaults

source/reference/exit-codes.txt

@@ -36,7 +36,7 @@ issues with :binary:`~bin.mongod` and :binary:`~bin.mongos` instances.
    * - .. error:: 3
      - Returned by :binary:`~bin.mongod` if there is a mismatch
        between hostnames specified on the command line and in the
-       :data:`local.sources` collection, in master/slave mode.
+       ``local.sources`` collection, in master/slave mode.
 
        .. symbol: EXIT_REPLICATION_ERROR = 3
 

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

@@ -462,14 +462,14 @@ This method performs the following actions:
 #. The ``query`` finds a document in the ``people`` collection
    where the ``name`` field has the value ``Tom``, the ``state``
    field has the value ``active`` and the ``rating`` field has a
-   value :operator:`greater than <$gt>` 10.
+   value :query:`greater than <$gt>` 10.
 
 #. The ``sort`` orders the results of the query in ascending order.
    If multiple documents meet the ``query`` condition, the method
    will select for modification the first document as ordered by
    this ``sort``.
 
-#. The update :operator:`increments <$inc>` the value of the
+#. The update :update:`increments <$inc>` the value of the
    ``score`` field by 1.
 
 #. The method returns the original (i.e. pre-modification) document