DOCSP-23877 Fix v4.2 build errors (#1486)

* WIP:

* WIP

* add missing ref

* more fixes

* more fixes

* more fixes

Author: jeff-allen-mongo

config/intersphinx.yaml

@@ -1,5 +1,5 @@
 name: pymongo
-url: https://api.mongodb.com/python/current/
+url: https://pymongo.readthedocs.io/en/stable/
 path: pymongo.inv
 ---
 name: motor

source/about.txt

@@ -52,10 +52,10 @@ Manual. You can see the full revision history and track ongoing
 improvements and additions for all versions of the manual from its `GitHub
 repository <https://github.com/mongodb/docs>`_.
 
-This edition reflects "|branch|" branch of the documentation
-as of the "|commit|" revision. This branch is explicitly accessible
-via "|hardlink|" and you can always reference the commit of the
-current manual in the :hardlink:`release.txt` file.
+This edition reflects "|branch|" branch of the documentation. This
+branch is explicitly accessible via "|hardlink|" and you can always
+reference the commit of the current manual in the
+:hardlink:`release.txt` file.
 
 The most up-to-date, current, and stable version of the manual is
 always available at "https://docs.mongodb.com/manual/".
@@ -108,4 +108,3 @@ For more information on the MongoDB documentation process, see the
 
 If you have any questions, please feel free to open a :issue:`Jira Case
 <DOCS>`.
-

source/core/index-compound.txt

@@ -88,13 +88,14 @@ as well as both ``item`` and ``stock`` fields:
 For details, see :ref:`compound-index-prefix`.
 
 .. index:: index; sort order
-.. _index-ascending-and-descending:
 
 The order of the indexed fields has a strong impact on the
 effectiveness of a particular index for a given query. For most
 compound indexes, following the :ref:`ESR (Equality, Sort, Range) rule
 <esr-indexing-rule>` helps to create efficient indexes.
 
+.. _index-ascending-and-descending:
+
 Sort Order
 ----------
 
@@ -203,4 +204,3 @@ Additional Considerations
 -------------------------
 
 .. include:: /includes/index-tutorials-considerations.rst
-

source/includes/fact-platform-support-enterprise-windows.rst

@@ -16,5 +16,4 @@ MongoDB only supports the 64-bit versions of these platforms.
 
 See :ref:`prod-notes-supported-platforms` for more information.
 
-.. include:: includes/fact-wsl-not-supported.rst
-
+.. include:: /includes/fact-wsl-not-supported.rst

source/includes/fact-platform-support-windows.rst

@@ -16,5 +16,4 @@ MongoDB only supports the 64-bit versions of these platforms.
 
 See :ref:`prod-notes-supported-platforms` for more information.
 
-.. include:: includes/fact-wsl-not-supported.rst
-
+.. include:: /includes/fact-wsl-not-supported.rst

source/includes/fact-sort-consistency.rst

@@ -0,0 +1,7 @@
+MongoDB does not store documents in a collection in a particular order.
+When sorting on a field which contains duplicate values, documents
+containing those values may be returned in any order.
+
+If consistent sort order is desired, include at least one field in your
+sort that contains unique values. The easiest way to guarantee this is
+to include the ``_id`` field in your sort query.

source/includes/important-delayed-replica-set-members.rst

@@ -29,6 +29,4 @@
 
    For more information on the majority commit point, see 
    :doc:`Causal Consistency and Read and Write Concerns
-   </core/causal-consistency-read-write-concerns>`. For additional 
-   details on resolving performance issues see the
-   :ref:`replica set maintenance tutorial<performance-issues-psa>`.
+   </core/causal-consistency-read-write-concerns>`.

source/reference/command/splitChunk.txt

@@ -264,9 +264,7 @@ Glossary
    DDL (Data Definition Language)
       DDL includes commands that create and modify collections and
       indexes. For the full list of commands, see
-      :ref:`transactions-operations-ddl-explicit`,
-      :ref:`transactions-operations-ddl-implicit`, and
-      :ref:`txn-prod-considerations-ddl`.
+      :ref:`transactions-operations-ref`.
 
    delayed member
       A :term:`replica set` member that cannot become primary and

source/reference/glossary.txt

@@ -215,13 +215,6 @@ Indexes
 
    .. include:: /includes/extracts/collation-index-type-restrictions-addendum.rst
 
-.. limit:: Hidden Indexes
-
-   - You cannot :doc:`hide </core/index-hidden>` the ``_id`` index.
-
-   - You cannot use :method:`~cursor.hint()` on a :doc:`hidden index
-     </core/index-hidden>`.
-
 Sorts
 -----
 

source/reference/limits.txt

@@ -733,10 +733,10 @@ Options
 
 
    By default, :program:`mongodump` uses the ``_id`` index when scanning
-   collections with that index is available (e.g. 
-   :ref:`3.4-reference-views` do not have any indexes). Specify :option:`--forceTableScan` 
-   to direct :program:`mongodump` to scan collection data without the use of the 
-   ``_id`` index. 
+   collections with that index is available (for example, :ref:`views
+   <views-landing-page>` do not have any indexes). Specify
+   :option:`--forceTableScan` to direct :program:`mongodump` to scan
+   collection data without the use of the ``_id`` index. 
 
    :option:`--forceTableScan` does not ensure a point-in-time snapshot. Use
    :option:`--oplog` to create a point-in-time snapshot.

source/reference/program/mongodump.txt

@@ -155,17 +155,17 @@ current working directory.
 Create Backups Using Oplogs
 ```````````````````````````
 
-The :option:`--oplog <mongodump.--oplog>` option with
+The :option:`--oplog <mongodump --oplog>` option with
 :binary:`~bin.mongodump` collects the :term:`oplog` entries and allows
 you to perform a backup on a live database. If you later restore the
 database from the backup, the database will be the same as it was when
 the backup process completed.
 
-With :option:`--oplog <mongodump.--oplog>`, :binary:`~bin.mongodump`
+With :option:`--oplog <mongodump --oplog>`, :binary:`~bin.mongodump`
 copies all the data from the source database as well as all of the
 :term:`oplog` entries from the beginning to the end of the backup
 procedure. This operation, in conjunction with :option:`mongorestore
---oplogReplay <mongorestore.--oplogReplay>`, allows you to restore a
+--oplogReplay <mongorestore --oplogReplay>`, allows you to restore a
 backup that reflects the specific moment in time that corresponds to
 when :binary:`~bin.mongodump` completed creating the dump file.
 
@@ -245,9 +245,9 @@ running on the localhost interface on the default port ``27017``.
 Restore Point in Time Oplog Backup
 ``````````````````````````````````
 
-If you created your database dump using the :option:`--oplog
-<mongodump --oplog>` option to ensure a point-in-time snapshot, call
-:binary:`~bin.mongorestore` with the
+If you created your database dump using the
+:option:`--oplog <mongodump --oplog>` option to ensure a point-in-time
+snapshot, call :binary:`~bin.mongorestore` with the
 :option:`--oplogReplay <mongorestore --oplogReplay>`
 option, as in the following example:
 
@@ -287,6 +287,3 @@ prompt for the password:
 .. code-block:: sh
 
    mongorestore --host=mongodb1.example.net --port=3017 --username=user  --authenticationDatabase=admin /opt/backup/mongodump-2013-10-24
-
-
-