Merge pull request #40 from ccho-mongodb/111920-fix-snooty-errors

111920 fix snooty errors

Author: Chris Cho

source/fundamentals/auth.txt

@@ -345,4 +345,4 @@ mechanism:
 
 For additional information on configuring your application to use
 certificates as well as TLS/SSL options, see our
-:doc:`TLS/SSL guide </fundamentals/connection>`.
+:doc:`TLS/SSL guide </fundamentals/connection/tls>`.

source/fundamentals/connection.txt

@@ -2,26 +2,28 @@
 Connection Guide
 ================
 
-.. contents:: On this page
-   :local:
-   :backlinks: none
-   :depth: 2
-   :class: singlecol
+.. default-domain:: mongodb
 
 .. toctree::
 
    /fundamentals/connection/tls
    /fundamentals/connection/jndi
 
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
 This guide shows you how to connect to a MongoDB instance or replica set
 deployment using the driver.
 
 For information about authenticating with a MongoDB instance,
 see :doc:`Authentication </fundamentals/auth>`. To learn more about using
 the driver with the Java Naming and Directory Interface (JNDI), see
-:doc:`JNDI <fundamentals/connection/jndi>`. To configure TLS/SSL security
+:doc:`JNDI </fundamentals/connection/jndi>`. To configure TLS/SSL security
 for connections to your MongoDB instance, see :doc:`TLS/SSL
-<fundamentals/connection/tls>`.
+</fundamentals/connection/tls>`.
 
 .. _mongoclient:
 

source/fundamentals/connection/jndi.txt

@@ -1,5 +1,3 @@
-.. _jndi:
-
 Java Naming and Directory Interface (JNDI)
 ==========================================
 

source/fundamentals/connection/tls.txt

@@ -1,5 +1,3 @@
-.. _tls:
-
 ==============================
 Enable TLS/SSL on a Connection
 ==============================
@@ -14,8 +12,8 @@ You can connect to MongoDB instances with the
 `TLS/SSL <https://en.wikipedia.org/wiki/Transport_Layer_Security>`__
 security protocol using the underlying TLS/SSL support in the JDK. To
 configure your connection to use TLS/SSL, enable the TLS/SSL settings in
-either the :java-docs:`ConnectionString <apidocs/mongodb-driver-core/com/mongodb/ConnectionString.html>
-or :java-docs:`MongoClientSettings <apidocs/mongodb-driver-core/com/mongodb/MongoClientSettings.html>.
+either the :java-docs:`ConnectionString <apidocs/mongodb-driver-core/com/mongodb/ConnectionString.html>`
+or :java-docs:`MongoClientSettings <apidocs/mongodb-driver-core/com/mongodb/MongoClientSettings.html>`.
 
 .. note:: Debugging TLS/SSL
 

source/fundamentals/data-formats/document-data-format-pojo.txt

@@ -125,7 +125,7 @@ To set up the driver to store and retrieve POJOs, we need to specify:
 - A ``MongoClient``, ``MongoDatabase``, or ``MongoCollection`` instance
   configured to use the ``CodecRegistry``.
 - A ``MongoCollection`` instance created with the POJO document class
-  bound to the :java-docs:`TDocument </apidocs/mongodb-driver-sync/com/mongodb/client/MongoCollection.html>`__
+  bound to the :java-docs:`TDocument </apidocs/mongodb-driver-sync/com/mongodb/client/MongoCollection.html>`
   generic type.
 
 Follow the steps below to see how to perform each of the configuration

source/usage-examples/watch.txt

@@ -65,8 +65,7 @@ The callback function triggers when a change event is emitted. You can
 specify logic in the callback to process the event document when it is
 received.
 
-.. admonition:: forEach() blocks the current thread
-   :class: important
+.. important:: forEach() blocks the current thread
 
    Calls to ``forEach()`` block the current thread as long as the
    corresponding change stream listens for events. If your program
@@ -174,4 +173,4 @@ methods presented above:
 - :java-sync-api:`ChangeStreamIterable <com/mongodb/client/ChangeStreamIterable.html>`
 - :java-sync-api:`MongoCollection.watch() <com/mongodb/client/MongoCollection.html#watch()>`
 - :java-sync-api:`MongoDatabase.watch() <com/mongodb/client/MongoDatabase.html#watch()>`
-- :java-sync-api:`MongoClient.watch() <com/mongodb/client/MongoClient.html#watch()>`
+- :java-sync-api:`MongoClient.watch() <com/mongodb/client/MongoClient.html#watch()>`