DOCSP-3768 update links to drivers

skerschb · kay-kim · commit b44765de1c1f · 2018-11-27T10:51:42.000-05:00
diff --git a/source/core/document.txt b/source/core/document.txt
@@ -75,11 +75,11 @@ Field names are strings.
 .. include:: /includes/fact-document-field-name-restrictions.rst
 
 BSON documents may have more than one field with the same name.
-Most :doc:`MongoDB interfaces </applications/drivers>`, however, represent MongoDB
+Most :ecosystem:`MongoDB interfaces </drivers>`, however, represent MongoDB
 with a structure (e.g. a hash table) that does not support duplicate
 field names. If you need to manipulate documents that have more than one
-field with the same name, see the :doc:`driver documentation
-</applications/drivers>` for your driver.
+field with the same name, see the :ecosystem:`driver documentation
+</drivers>` for your driver.
 
 Some documents created by internal MongoDB processes may have duplicate
 fields, but *no* MongoDB process will *ever* add duplicate fields to an
diff --git a/source/core/gridfs.txt b/source/core/gridfs.txt
@@ -71,11 +71,11 @@ can update the metadata field that indicates "latest" status in an
 atomic update after uploading the new version of the file, and later
 remove previous versions if needed.
 
-Furthermore, if your files are all smaller the 16 MB :limit:`BSON
-Document Size` limit, consider storing the file manually within a
-single document instead of using GridFS. You may use the BinData data
-type to store the binary data. See your :doc:`drivers
-</applications/drivers>` documentation for details on using BinData.
+Furthermore, if your files are all smaller than the 16 MB :limit:`BSON
+Document Size` limit, consider storing each file in a single document instead
+of using GridFS. You may use the BinData data type to store the binary data.
+See your :ecosystem:`drivers </drivers>` documentation for details on
+using BinData.
 
 .. index:: GridFS; initialize
 .. _gridfs-use:
@@ -86,7 +86,7 @@ Use GridFS
 To store and retrieve files using :term:`GridFS`, use either of the
 following:
 
-- A MongoDB driver. See the :doc:`drivers</applications/drivers>`
+- A MongoDB driver. See the :ecosystem:`drivers</drivers>`
   documentation for information on using GridFS with your driver.
 
 - The :binary:`~bin.mongofiles` command-line tool. See the
@@ -236,7 +236,7 @@ GridFS Indexes
 --------------
 
 GridFS uses indexes on each of the ``chunks`` and ``files`` collections
-for efficiency. :doc:`Drivers </applications/drivers>` that conform to
+for efficiency. :ecosystem:`Drivers </drivers>` that conform to
 the `GridFS specification`_ automatically create these indexes for
 convenience. You can also create any additional indexes as desired to
 suit your application's needs.
@@ -255,7 +255,7 @@ chunks, as demonstrated in the following example:
 
    db.fs.chunks.find( { files_id: myFileID } ).sort( { n: 1 } )
 
-:doc:`Drivers </applications/drivers>` that conform to the `GridFS
+:ecosystem:`Drivers </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.
@@ -280,7 +280,7 @@ efficient retrieval of files, as shown in this example:
 
    db.fs.files.find( { filename: myFileName } ).sort( { uploadDate: 1 } )
 
-:doc:`Drivers </applications/drivers>` that conform to the `GridFS
+:ecosystem:`Drivers </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.
diff --git a/source/core/read-preference.txt b/source/core/read-preference.txt
@@ -112,7 +112,7 @@ Read Preference Modes
    [#edge-cases-2-primaries]_ Ensure that your application can tolerate
    stale data if you choose to use a non-:readmode:`primary` mode.
 
-MongoDB :doc:`drivers </applications/drivers>` support five
+MongoDB :ecosystem:`drivers </drivers>` support five
 read preference modes.
 
 .. include:: /includes/read-preference-modes-table.rst
diff --git a/source/core/shell-types.txt b/source/core/shell-types.txt
@@ -11,7 +11,7 @@ Data Types in the ``mongo`` Shell
    :class: singlecol
 
 MongoDB :term:`BSON` provides support for additional data types than
-:term:`JSON`. :doc:`Drivers </applications/drivers>` provide native
+:term:`JSON`. :ecosystem:`Drivers </drivers>` provide native
 support for these data types in host languages and the
 :binary:`~bin.mongo` shell also provides several helper classes to support
 the use of these data types in the :binary:`~bin.mongo` JavaScript
diff --git a/source/core/tailable-cursors.txt b/source/core/tailable-cursors.txt
@@ -50,5 +50,5 @@ Consider the following behaviors related to tailable cursors:
 
   A *dead* cursor has an id of ``0``.
 
-See your :doc:`driver documentation </applications/drivers>` for the
+See your :ecosystem:`driver documentation </drivers>` for the
 driver-specific method to specify the tailable cursor.
diff --git a/source/faq/fundamentals.txt b/source/faq/fundamentals.txt
@@ -149,7 +149,7 @@ object, not a string. Thus traditional SQL injection attacks are not a
 problem. More details and some nuances are covered below.
 
 MongoDB represents queries as :term:`BSON` objects. Typically
-:doc:`client libraries </applications/drivers>` provide a convenient,
+:ecosystem:`client libraries </drivers>` provide a convenient,
 injection free, process to build these objects. Consider the following
 C++ example:
 
diff --git a/source/includes/apiargs-method-cursor.addOption-param.yaml b/source/includes/apiargs-method-cursor.addOption-param.yaml
@@ -2,7 +2,7 @@ arg_name: param
 description: |
   ``OP_QUERY`` wire protocol flag. For the :binary:`~bin.mongo` shell,
   you can use the cursor flags listed below. For the driver-specific
-  list, see your :doc:`driver documentation </applications/drivers>`.
+  list, see your :ecosystem:`driver documentation </drivers>`.
 interface: method
 name: flag
 operation: cursor.addOption
diff --git a/source/includes/extracts-parent-admonition-js-prevalence.yaml b/source/includes/extracts-parent-admonition-js-prevalence.yaml
@@ -6,6 +6,6 @@ content: |
   
      Although {{javascriptUsingOperation}} JavaScript, most
      interactions with MongoDB do not use JavaScript but use an
-     :doc:`idiomatic driver </applications/drivers>` in the language
+     :ecosystem:`idiomatic driver </drivers>` in the language
      of the interacting application.
 ...
diff --git a/source/includes/fact-document-max-size.rst b/source/includes/fact-document-max-size.rst
@@ -4,5 +4,5 @@ The maximum document size helps ensure that a single document cannot
 use excessive amount of RAM or, during transmission, excessive amount
 of bandwidth. To store documents larger than the maximum size, MongoDB
 provides the GridFS API. See :binary:`~bin.mongofiles` and the
-documentation for your :doc:`driver </applications/drivers>` for more
+documentation for your :ecosystem:`driver </drivers>` for more
 information about GridFS.
diff --git a/source/includes/options-mongos.yaml b/source/includes/options-mongos.yaml
@@ -242,8 +242,8 @@ description: |
   {{intro}} ping time, in milliseconds, that :binary:`~bin.mongos` uses
   to determine which secondary replica set members to pass read
   operations from clients. The default value of ``15`` corresponds to
-  the default value in all of the client :doc:`drivers
-  </applications/drivers>`.
+  the default value in all of the client :ecosystem:`drivers
+  </drivers>`.
 
   When :binary:`~bin.mongos` receives a request that permits reads to
   :term:`secondary` members, the :binary:`~bin.mongos` will:
diff --git a/source/reference/connection-string.txt b/source/reference/connection-string.txt
@@ -15,8 +15,8 @@ Connection String URI Format
    :class: singlecol
 
 This document describes the URI format for defining connections between
-applications and MongoDB instances in the official MongoDB :doc:`drivers
-</applications/drivers>`.
+applications and MongoDB instances in the official MongoDB :ecosystem:`drivers
+</drivers>`.
 
 .. index:: connections; connection string format
 .. _connections-standard-connection-string-format:
@@ -27,7 +27,7 @@ Standard Connection String Format
 This section describes the standard format of the MongoDB connection URI
 used to connect to a MongoDB database server. The format is the same for
 all official MongoDB drivers. For a list of drivers and links to driver
-documentation, see :doc:`/applications/drivers`.
+documentation, see :ecosystem:`/drivers`.
 
 The following is the standard URI connection scheme:
 
@@ -198,22 +198,22 @@ Connection Options
 
        .. note::
           The :urioption:`ssl` option is not supported by all drivers.
-          See your :doc:`driver </applications/drivers>` documentation
+          See your :ecosystem:`driver </drivers>` documentation
           and the :doc:`/tutorial/configure-ssl` document.
 
    * - .. urioption:: connectTimeoutMS
 
      - The time in milliseconds to attempt a connection before timing
        out. The default is never to timeout, though different drivers
-       might vary. See the :doc:`driver </applications/drivers>`
+       might vary. See the :ecosystem:`driver </drivers>`
        documentation.
 
    * - .. urioption:: socketTimeoutMS
 
      - The time in milliseconds to attempt a send or receive on a
        socket before the attempt times out. The default is never to
        timeout, though different drivers might vary. See the
-       :doc:`driver </applications/drivers>` documentation.
+       :ecosystem:`driver </drivers>` documentation.
 
 .. _connection-pool-options:
 
@@ -222,7 +222,7 @@ Connection Pool Options
 
 Most drivers implement some kind of connection pool handling. 
 Some drivers do not support connection
-pools. See your :doc:`driver </applications/drivers>` documentation
+pools. See your :ecosystem:`driver </drivers>` documentation
 for more information on the connection pooling implementation. These
 options allow applications to configure the connection pool when
 connecting to the MongoDB deployment.
@@ -247,7 +247,7 @@ connecting to the MongoDB deployment.
        .. note::
           The :urioption:`minPoolSize` option is not supported by all
           drivers. For information on your driver, see the
-          :doc:`drivers </applications/drivers>` documentation.
+          :ecosystem:`drivers </drivers>` documentation.
 
    * - .. urioption:: maxIdleTimeMS
 
@@ -261,14 +261,14 @@ connecting to the MongoDB deployment.
      - A number that the driver multiples the :urioption:`maxPoolSize`
        value to, to provide the maximum number of threads allowed to
        wait for a connection to become available from the pool. For
-       default values, see the :doc:`/applications/drivers`
+       default values, see the :ecosystem:`/drivers`
        documentation.
 
    * - .. urioption:: waitQueueTimeoutMS
 
      - The maximum time in milliseconds that a thread can wait for a
        connection to become available. For default values, see the
-       :doc:`/applications/drivers` documentation.
+       :ecosystem:`/drivers` documentation.
 
 .. _connections-write-concern:
 
@@ -598,13 +598,13 @@ Miscellaneous Configuration
        ``pythonLegacy``
          The default representation for the Python driver.
 
-       For the default, see the :doc:`drivers </applications/drivers>`
+       For the default, see the :ecosystem:`drivers </drivers>`
        documentation for your driver.
 
        .. note::
           Not all drivers support the :urioption:`uuidRepresentation`
-          option. For information on your driver, see the :doc:`drivers
-          </applications/drivers>` documentation.
+          option. For information on your driver, see the :ecosystem:`drivers
+          </drivers>` documentation.
 
 .. _connections-connection-examples:
 
@@ -657,7 +657,7 @@ The following connects to a UNIX domain socket with file path
    mongodb://%2Ftmp%2Fmongodb-27017.sock
 
 .. note:: Not all drivers support UNIX domain sockets. For information
-   on your driver, see the :doc:`drivers </applications/drivers>`
+   on your driver, see the :ecosystem:`drivers </drivers>`
    documentation.
 
 Replica Set with Members on Different Machines
diff --git a/source/reference/database-references.txt b/source/reference/database-references.txt
@@ -46,7 +46,7 @@ MongoDB applications use one of two methods for relating documents:
 
    To resolve DBRefs, your application
    must perform additional queries to return the referenced
-   documents. Many :doc:`drivers </applications/drivers>` have helper
+   documents. Many :ecosystem:`drivers </drivers>` have helper
    methods that form the query for the DBRef automatically. The
    drivers [#official-driver]_ do not *automatically* resolve DBRefs
    into documents.
diff --git a/source/reference/glossary.txt b/source/reference/glossary.txt
@@ -268,7 +268,7 @@ Glossary
 
    driver
       A client library for interacting with MongoDB in a particular
-      language. See :doc:`/applications/drivers`.
+      language. See :ecosystem:`/drivers`.
 
    durable
       A write operation is durable when it will persist across a
diff --git a/source/reference/method/cursor.batchSize.txt b/source/reference/method/cursor.batchSize.txt
@@ -19,8 +19,8 @@ Definition
    number of documents to return in each batch of the response from the
    MongoDB instance. In most cases, modifying the batch size will
    not affect the user or the application, as the
-   :binary:`~bin.mongo` shell and most :doc:`drivers
-   </applications/drivers>` return results as if MongoDB returned a
+   :binary:`~bin.mongo` shell and most :ecosystem:`drivers
+   </drivers>` return results as if MongoDB returned a
    single batch.
 
    The :method:`~cursor.batchSize()` method takes the
diff --git a/source/reference/method/db.collection.find.txt b/source/reference/method/db.collection.find.txt
@@ -75,8 +75,8 @@ automatically iterates the cursor to display up to the first 20
 documents. Type ``it`` to continue iteration.
 
 To access the returned documents with a driver, use the appropriate
-cursor handling mechanism for the :doc:`driver language
-</applications/drivers>`.
+cursor handling mechanism for the :ecosystem:`driver language
+</drivers>`.
 
 Read Concern
 ~~~~~~~~~~~~
@@ -516,8 +516,8 @@ to iterate the cursor and access the documents:
 Modify the Cursor Behavior
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The :binary:`~bin.mongo` shell and the :doc:`drivers
-</applications/drivers>` provide several cursor methods that call on the
+The :binary:`~bin.mongo` shell and the :ecosystem:`drivers
+</drivers>` provide several cursor methods that call on the
 *cursor* returned by the :method:`~db.collection.find()` method to
 modify its behavior.
 
diff --git a/source/release-notes/2.0.txt b/source/release-notes/2.0.txt
@@ -321,7 +321,7 @@ New ``ContinueOnError`` Option for Bulk Insert
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Set the ``continueOnError`` option for bulk inserts, in the
-:doc:`driver </applications/drivers>`, so that bulk insert will
+:ecosystem:`driver </drivers>`, so that bulk insert will
 continue to insert any remaining documents even if an insert fails, as
 is the case with  duplicate key exceptions or network interruptions. The :dbcommand:`getLastError`
 command will report whether any inserts have failed, not just the
diff --git a/source/release-notes/2.2.txt b/source/release-notes/2.2.txt
@@ -25,7 +25,7 @@ Synopsis
 
 - :binary:`~bin.mongod`, 2.2 is a drop-in replacement for 2.0 and 1.8.
 
-- Check your :doc:`driver </applications/drivers>` documentation for
+- Check your :ecosystem:`driver </drivers>` documentation for
   information regarding required compatibility upgrades, and always
   run the recent release of your driver.
 
diff --git a/source/tutorial/aggregation-zip-code-data-set.txt b/source/tutorial/aggregation-zip-code-data-set.txt
@@ -62,7 +62,7 @@ the stages in sequence.
 The :method:`aggregate() <db.collection.aggregate()>` method in the
 :binary:`~bin.mongo` shell provides a wrapper around the
 :dbcommand:`aggregate` database command. See the documentation for your
-:doc:`driver </applications/drivers>` for a more idiomatic interface
+:ecosystem:`driver </drivers>` for a more idiomatic interface
 for data aggregation operations.
 
 .. _aggregation-return-states-by-population:
diff --git a/source/tutorial/manage-the-database-profiler.txt b/source/tutorial/manage-the-database-profiler.txt
@@ -64,8 +64,8 @@ Enable Database Profiling and Set the Profiling Level
 
 You can enable database profiling from the :binary:`~bin.mongo` shell or
 through a driver using the :dbcommand:`profile` command. This section
-will describe how to do so from the :binary:`~bin.mongo` shell. See your :doc:`driver documentation
-</applications/drivers>` if you want to control the profiler from
+will describe how to do so from the :binary:`~bin.mongo` shell. See your :ecosystem:`driver documentation
+</drivers>` if you want to control the profiler from
 within your application.
 
 When you enable profiling, you also set the :ref:`profiling level
diff --git a/source/tutorial/upgrade-revision.txt b/source/tutorial/upgrade-revision.txt
@@ -57,7 +57,7 @@ use the procedure :ref:`upgrade-mongodb-instance`.
 Follow this upgrade procedure:
 
 1. For deployments that use authentication, first upgrade all of your
-   MongoDB :doc:`drivers </applications/drivers>`. To upgrade, see the
+   MongoDB :ecosystem:`drivers </drivers>`. To upgrade, see the
    documentation for your driver as well as the :ecosystem:`Driver
    Compatibility </drivers/driver-compatibility-reference>` page.
 
diff --git a/source/tutorial/use-database-commands.txt b/source/tutorial/use-database-commands.txt
@@ -45,7 +45,7 @@ commands called :method:`db.runCommand()`. The following operation in
 
    db.runCommand( { isMaster: 1 } )
 
-Many :doc:`drivers </applications/drivers>` provide an equivalent for
+Many :ecosystem:`drivers </drivers>` provide an equivalent for
 the :method:`db.runCommand()` method. Internally, running commands
 with :method:`db.runCommand()` is equivalent to a special query
 against the :term:`$cmd` collection.
