From: Tatsuo Ishii <ishii@postgresql.org>
Date: Thu, 13 Oct 2016 22:45:25 +0000 (+0900)
Subject: Fix typo.
X-Git-Tag: REL_10_BETA1~1565
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b1ee762a6138df073d4b2b80c235dd9025a8532c;p=postgresql

Fix typo.

Confirmed by Tom Lane.
---

diff --git a/doc/src/sgml/parallel.sgml b/doc/src/sgml/parallel.sgml
index 1e71529eeb..94170b770b 100644
--- a/doc/src/sgml/parallel.sgml
+++ b/doc/src/sgml/parallel.sgml
@@ -189,7 +189,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
     Even when parallel query plan is generated for a particular query, there
     are several circumstances under which it will be impossible to execute
     that plan in parallel at execution time.  If this occurs, the leader
-    will execute the portion of the plan between below the <literal>Gather</>
+    will execute the portion of the plan below the <literal>Gather</>
     node entirely by itself, almost as if the <literal>Gather</> node were
     not present.  This will happen if any of the following conditions are met:
   </para>