merge: typos

Author: Sam Kleinman

source/faq/fundamentals.txt

@@ -220,7 +220,7 @@ If you're running a 64-bit build of MongoDB, there's virtually no
 limit to storage size. For production deployments, 64-bit builds and
 operating systems are strongly recommended.
 
-.. seealso:: "`Blog Post: 32-bit Limitations <http://blog.mongodb.org/post/137788967/32-bit-limitations>`_
+.. seealso:: "`Blog Post: 32-bit Limitations <http://blog.mongodb.org/post/137788967/32-bit-limitations>`_"
 
 .. note::
 

source/reference/connection-string.txt

@@ -31,14 +31,14 @@ The components of this string are:
 
 #. ``mongodb://``
 
-    A required prefix to identify that this is a string in the standard
-    connection format.
+   A required prefix to identify that this is a string in the standard
+   connection format.
 
 #. ``username:password@``
 
-  Optional. If specified, the client will attempt to log in to the
-  specific database using these credentials after connecting to the
-  :program:`mongod` instance.
+   Optional. If specified, the client will attempt to log in to the
+   specific database using these credentials after connecting to the
+   :program:`mongod` instance.
 
 #. ``host1``
 

source/use-cases/storing-log-data.txt

@@ -617,7 +617,7 @@ use a :term:`sharded cluster`, which takes advantage of MongoDB's
 :term:`sharding` functionality. This section introduces the unique
 sharding concerns for this event logging case.
 
-.. seealso:: ":doc:`/faq/sharding`" and the ":wiki:`Sharding` wiki
+.. seealso:: ":doc:`/faq/sharding`" and the ":wiki:`Sharding`" wiki
    page.
 
 Limitations