From 9b4c401d04290b8f775a1e4ef58265939939bb28 Mon Sep 17 00:00:00 2001
From: Darren Evenson <darrene@clickiqinc.com>
Date: Tue, 6 Aug 2013 10:45:06 -0500
Subject: [PATCH] HHH-8427 Typo in documentation - Basic Mapping

---
 .../src/main/docbook/manual/en-US/content/basic_mapping.xml   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/src/main/docbook/manual/en-US/content/basic_mapping.xml b/documentation/src/main/docbook/manual/en-US/content/basic_mapping.xml
index e5e2a518eb..f7a9e42c4f 100644
--- a/documentation/src/main/docbook/manual/en-US/content/basic_mapping.xml
+++ b/documentation/src/main/docbook/manual/en-US/content/basic_mapping.xml
@@ -2316,7 +2316,7 @@ public class Flight implements Serializable {
       </section>
     </section>
 
-    <section xml:id="mapping-declaration-property" revision="4">
+    <section xml:id="mapping-declaration-property" revision="5">
       <title>Property</title>
 
       <para>You need to decide which property needs to be made persistent in a
@@ -2550,7 +2550,7 @@ public class MonetaryAmount implements Serializable {
           the position of the <classname>@Id</classname> or
           <classname>@EmbeddedId</classname> annotations. If these annotations
           are on a field, then only fields are considered for persistence and
-          the state is accessed via the field. If there annotations are on a
+          the state is accessed via the field. If these annotations are on a
           getter, then only the getters are considered for persistence and the
           state is accessed via the getter/setter. That works well in practice
           and is the recommended approach.<note>