summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Riggs2012-10-17 08:21:29 +0000
committerSimon Riggs2012-10-17 08:21:29 +0000
commitdf35b7e33ef6354ef8530ba9eabcdb2010b0ca39 (patch)
treea917657e22a7f4e4194f873ce26d17501ceb4ced
parent98188441972151995d485b2e2c18a8cf36a3a227 (diff)
Fix typo in previous commit
-rw-r--r--doc/src/sgml/indices.sgml2
-rw-r--r--doc/src/sgml/ref/create_index.sgml2
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>