From: Simon Riggs <simon@2ndQuadrant.com>
Date: Wed, 17 Oct 2012 08:20:42 +0000 (+0100)
Subject: Fix typo in previous commit
X-Git-Tag: REL9_1_7~47
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f34d1fa0c8bd587a165234e0971bba8dc5e1fd2a;p=postgresql

Fix typo in previous commit
---

diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index c7c3211f1f..fa479e6ab8 100644
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -199,7 +199,7 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
     after a database crash if there were unwritten changes.
     Also, changes to hash indexes are not replicated over streaming or
     file-based replication after the initial base backup, so they
-    give wrong anwers to queries that subsequently use them.
+    give wrong answers to queries that subsequently use them.
     For these reasons, hash index use is presently discouraged.
    </para>
   </caution>
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 8f266ed6d0..8a59a9fd82 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -458,7 +458,7 @@ Indexes:
     after a database crash if there were unwritten changes.
     Also, changes to hash indexes are not replicated over streaming or
     file-based replication after the initial base backup, so they
-    give wrong anwers to queries that subsequently use them.
+    give wrong answers to queries that subsequently use them.
     For these reasons, hash index use is presently discouraged.
    </para>
   </caution>