postgres.git / summary / log / commit / refs

commit    df35b7e33ef6354ef8530ba9eabcdb2010b0ca39
Author:   Simon Riggs <simon@2ndQuadrant.com>
Date:     Wed Oct 17 08:21:29 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 9e090af0a0f..c4abaf894d1 100644
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -194,7 +194,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 06bd06ba7c9..701f6513683 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -446,7 +446,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: 981884419721]