From 4f17abe6ffc702bb54f9da7773d92b549b350018 Mon Sep 17 00:00:00 2001
From: Marijn van der Zee <marijn@serraict.com>
Date: Thu, 13 Oct 2011 16:14:27 +0200
Subject: [PATCH] Minor formatting change

---
 doc/reference/src/ado.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/reference/src/ado.xml b/doc/reference/src/ado.xml
index 4033a0e6..dd1fa659 100644
--- a/doc/reference/src/ado.xml
+++ b/doc/reference/src/ado.xml
@@ -1954,6 +1954,7 @@ public delegate T DataAdapterDelegate&lt;T&gt;(IDbDataAdapter dataAdapter);</pro
     order for them to correctly participate with a surrounding transactional
     context. The reason for this is by default the code generated is
     explicitly managing the connections and transactions. This issue is very
+    explicitly managing the connections and transactions. This issue is very
     well described in the article <ulink
     url="http://www.code-magazine.com/Article.aspx?quickid=0605031">System.Transactions
     and ADO.NET 2.0</ulink> by ADO.NET guru Sahil Malik. Spring offers a
@@ -2011,7 +2012,7 @@ public static void ApplyConnectionAndTx(object typedDataSetAdapter, IDbProvider
   <sect1 xml:id="ado-objects">
     <title>Database operations as Objects</title>
 
-    <para>The <literal>Spring.Data.Objects and Spring.Data.Objects.Generic
+    <para>The <literal>Spring.Data.Objects</literal> and <literal>Spring.Data.Objects.Generic
     </literal>namespaces contains classes that allow one to access the
     database in a more object-oriented manner. By way of an example, one can
     execute queries and get the results back as a list containing business