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

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

source/release-notes/2.2.txt

@@ -589,9 +589,9 @@ from a collection into memory. See: :issue:`SERVER-2023` and
 ``indexCounters`` No Longer Report Sampled Data
 ```````````````````````````````````````````````
 
-:data:`indexCounters` now report actual counters that reflect index
+``indexCounters`` now report actual counters that reflect index
 use and state. In previous versions, these data were sampled. See
-:issue:`SERVER-5784` and :data:`indexCounters` for more information.
+:issue:`SERVER-5784` and ``indexCounters`` for more information.
 
 Padding Specifiable on ``compact`` Command
 ``````````````````````````````````````````

source/release-notes/2.4-upgrade.txt

@@ -35,10 +35,10 @@ When upgrading, consider the following:
   will need to upgrade first to 2.2.1 and then upgrade to 2.4. See
   :ref:`2.4-upgrade-auth-limitation`.
 
-- If you have :data:`system.users` documents
+- If you have ``system.users`` documents
   (i.e. for :setting:`~security.authorization`) that you created before 2.4 you *must*
   ensure that there are no duplicate values for the ``user`` field in
-  the :data:`system.users` collection in
+  the ``system.users`` collection in
   *any* database.  If you *do* have documents with duplicate user
   fields, you must remove them before upgrading.
 

source/release-notes/2.6-changelog.txt

@@ -93,7 +93,7 @@ Sharding
 
 - :issue:`SERVER-17812` LockPinger has audit-related GLE failure
 - :issue:`SERVER-17805` logOp / OperationObserver should always check shardversion
-- :issue:`SERVER-17749` :dbcommand:`collMod` \ :collflag:`usePowerOf2Sizes` fails on :binary:`~bin.mongos`
+- :issue:`SERVER-17749` :dbcommand:`collMod` \ ``usePowerOf2Sizes`` fails on :binary:`~bin.mongos`
 - :issue:`SERVER-11980` Improve user cache invalidation enforcement on :binary:`~bin.mongos`
 
 Storage
@@ -111,7 +111,7 @@ Indexing
 Write Ops
 ~~~~~~~~~
 
-- :issue:`SERVER-18111` :binary:`~bin.mongod` allows user inserts into :data:`system.profile` collection
+- :issue:`SERVER-18111` :binary:`~bin.mongod` allows user inserts into ``system.profile`` collection
 - :issue:`SERVER-13542` Expose ``electionId`` on primary in :dbcommand:`isMaster`
 
 Networking
@@ -314,7 +314,7 @@ Querying
 - :issue:`SERVER-16291` Cannot set/list/clear index filters on the secondary
 - :issue:`SERVER-15958` The "isMultiKey" value is not correct in the output of aggregation explain plan
 - :issue:`SERVER-15899` Querying against path in document containing long array of subdocuments with nested arrays causes stack overflow
-- :issue:`SERVER-15696` :query:`$regex`, :query:`$in` and :query:`$sort` with index returns too many results
+- :issue:`SERVER-15696` :query:`$regex`, :query:`$in` and :update:`$sort` with index returns too many results
 - :issue:`SERVER-15639` Text queries can return incorrect results and leak memory when multiple predicates given on same text index prefix field
 - :issue:`SERVER-15580` Evaluating candidate query plans with concurrent writes on same collection may crash :binary:`~bin.mongod`
 - :issue:`SERVER-15528` Distinct queries can scan many index keys without yielding read lock
@@ -411,7 +411,7 @@ Querying
 - :issue:`SERVER-15286` Assertion in date indexes when opposite-direction-sorted and double "or" filtered
 - :issue:`SERVER-15279` Disable hash-based index intersection (AND_HASH) by default
 - :issue:`SERVER-15152` When evaluating plans, some index candidates cause complete index scan
-- :issue:`SERVER-15015` Assertion failure when combining :query:`$max` and :query:`$min` and reverse index scan
+- :issue:`SERVER-15015` Assertion failure when combining :operator:`$max` and :operator:`$min` and reverse index scan
 - :issue:`SERVER-15012` Server crashes on indexed rooted $or queries using a 2d index
 - :issue:`SERVER-14969` Dropping index during active aggregation operation can crash server
 - :issue:`SERVER-14961` Plan ranker favors intersection plans if predicate generates empty range index scan
@@ -646,7 +646,7 @@ Security
   includes privileges to run the :dbcommand:`collStats` command.
 
 - :issue:`SERVER-13804` The built-in role :authrole:`restore`
-  now has privileges on :data:`system.roles` collection.
+  now has privileges on :data:`admin.system.roles` collection.
 
 - :issue:`SERVER-13612` Fixed: "SSL-enabled server appears not to be
   sending the list of supported certificate issuers to the client"
@@ -774,7 +774,7 @@ Diagnostics
 ~~~~~~~~~~~
 
 - :issue:`SERVER-13587` Resolved: ":data:`~system.profile.ndeleted` in
-  :data:`system.profile` documents reports 1 too few documents
+  ``system.profile`` documents reports 1 too few documents
   removed"
 - :issue:`SERVER-13368` Improved exposure of timing information in
   :dbcommand:`currentOp`.
@@ -789,7 +789,7 @@ Tools
 ~~~~~
 
 - :issue:`SERVER-10464` :binary:`~bin.mongodump` can now query
-  :data:`oplog.$main` and :data:`oplog.rs` when using
+  ``oplog.$main`` and ``oplog.rs`` when using
   ``--dbpath``.
 - :issue:`SERVER-13760` :binary:`~bin.mongoexport` can now handle large
   timestamps on Windows.

source/release-notes/2.6-upgrade.txt

@@ -89,7 +89,7 @@ authentication and authorization:
   the role :authrole:`userAdminAnyDatabase`.
 
 - If your application performs CRUD operations on the
-  :data:`system.users` collection or uses a
+  ``system.users`` collection or uses a
   ``db.addUser()``\ -like method, then you **must**
   upgrade those drivers (i.e. client libraries) **before**
   :binary:`~bin.mongod` or :binary:`~bin.mongos` instances.

source/release-notes/2.6.txt

@@ -66,7 +66,7 @@ Minor Releases
 - Provide correct rollbacks for collection creation
   :issue:`SERVER-18211`
 
-- Allow user inserts into the :data:`system.profile` collection
+- Allow user inserts into the ``system.profile`` collection
   :issue:`SERVER-18211`
 
 - Fix to query system to ensure non-negation predicates get chosen
@@ -139,8 +139,8 @@ Minor Releases
 - Fixed: 2.6 :binary:`~bin.mongod` crashes with segfault when added to a 2.8 replica set
   with 12 or more members :issue:`SERVER-16107`
 
-- Fixed: :query:`$regex`, :query:`$in` and :query:`$sort` with index returns too
-  many results :issue:`SERVER-15696`
+- Fixed: :query:`$regex`, :query:`$in` and :update:`$sort` with index
+  returns too many results :issue:`SERVER-15696`
 
 - Change: :dbcommand:`moveChunk` will fail if there is data on the target
   shard and a required index does not exist.
@@ -155,7 +155,8 @@ Minor Releases
 2.6.5 -- October 07, 2014
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- :query:`$rename` now uses correct dotted source paths :issue:`SERVER-15029`
+- :update:`$rename` now uses correct dotted source paths
+  :issue:`SERVER-15029`
 
 - Partially written journal last section does not affect recovery
   :issue:`SERVER-15111`
@@ -518,7 +519,7 @@ Operational Changes
 Storage
 ~~~~~~~
 
-:collflag:`usePowerOf2Sizes` is now the default allocation strategy for
+``usePowerOf2Sizes`` is now the default allocation strategy for
 all new collections. The new allocation strategy uses more storage
 relative to total document size but results in lower levels of
 storage fragmentation and more predictable storage capacity planning
@@ -527,7 +528,7 @@ over time.
 To use the previous *exact-fit allocation strategy*:
 
 - For a specific collection, use :dbcommand:`collMod` with
-  :collflag:`usePowerOf2Sizes` set to ``false``.
+  ``usePowerOf2Sizes`` set to ``false``.
 
 - For all new collections on an entire :binary:`~bin.mongod` instance,
   set ``newCollectionsUsePowerOf2Sizes`` to ``false``.

source/release-notes/3.0-changelog.txt

@@ -328,7 +328,7 @@ Sharding
 ~~~~~~~~
 
 - :issue:`SERVER-17812` LockPinger has audit-related GLE failure
-- :issue:`SERVER-17749` :dbcommand:`collMod` :collflag:`usePowerOf2Sizes` fails on :binary:`~bin.mongos`
+- :issue:`SERVER-17749` :dbcommand:`collMod` ``usePowerOf2Sizes`` fails on :binary:`~bin.mongos`
 - :issue:`SERVER-16987` ``sh.getRecentMigrations`` shows aborted migration as success
 
 Storage

source/release-notes/4.2-downgrade-sharded-cluster.txt

@@ -126,9 +126,7 @@ Script to run on shards
 2d. Remove ``user_1_db_1`` System Unique Index
 ``````````````````````````````````````````````
 
-.. container::
-
-   .. include:: /includes/extracts/4.2-downgrade-fcv-system-unique-index.rst
+.. include:: /includes/extracts/4.2-downgrade-fcv-system-unique-index.rst
 
 2e. Remove Wildcard Indexes
 ```````````````````````````