postgres.git / summary / log / commit / refs

commit    f34d1fa0c8bd587a165234e0971bba8dc5e1fd2a
Author:   Simon Riggs <simon@2ndQuadrant.com>
Date:     Wed Oct 17 08:20:42 2012 +0000
First released in: 9.3.0, 8.3.22, 8.4.15, 9.0.11, 9.1.7, 9.2.2

    Fix typo in previous commit


 doc/src/sgml/indices.sgml          | 2 +-
 doc/src/sgml/ref/create_index.sgml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index c7c3211f1f1..fa479e6ab83 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 8f266ed6d00..8a59a9fd82e 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>


[parent: 3877b1fa17fc]