diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index 9eb948d6bcc..e6a14de5040 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 2403b7642a1..d800701ff4e 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -473,7 +473,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>