- fix typos

Change-Id: Ibf8bc0e997ff989c7b0c16afad48a95414078052

diff --git a/doc/build/faq/connections.rst b/doc/build/faq/connections.rst
index 40bef6a50a01549d8fb249a9c2777221882d6498..3c7175fe85b95db98c5bf4ed562be81cbb6a23e8 100644 (file)
--- a/doc/build/faq/connections.rst
+++ b/doc/build/faq/connections.rst
@@ -53,11 +53,15 @@ and replaced with a new connection when it is next checked out.
 For the more general case of accommodating database restarts and other
 temporary loss of connectivity due to network issues, connections that
 are in the pool may be recycled in response to more generalized disconnect
-detection techniques.  The section :ref:`:ref:`pool_disconnects` provides
+detection techniques.  The section :ref:`pool_disconnects` provides
 background on both "pessimistic" (e.g. pre-ping) and "optimistic"
 (e.g. graceful recovery) techniques.   Modern SQLAlchemy tends to favor
 the "pessimistic" approach.
 
+.. seealso::
+
+    :ref:`pool_disconnects`
+
 
 Why does SQLAlchemy issue so many ROLLBACKs?
 --------------------------------------------

diff --git a/lib/sqlalchemy/dialects/mysql/base.py b/lib/sqlalchemy/dialects/mysql/base.py
index d6701aeae4be0eb50499ac922b0ed5fce1e8b647..0cffae3895c1e3c5a6cee24cb9bd41b4eaf31eeb 100644 (file)
--- a/lib/sqlalchemy/dialects/mysql/base.py
+++ b/lib/sqlalchemy/dialects/mysql/base.py
@@ -42,7 +42,7 @@ be employed.  See :ref:`pool_disconnects` for current approaches.
 .. seealso::
 
     :ref:`pool_disconnects` - Background on several techniques for dealing
-     with timed out connections as well as database restarts.
+    with timed out connections as well as database restarts.
 
 .. _mysql_storage_engines: