summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-03-18 23:44:30 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-03-18 23:46:46 -0400
commit03ca8c249953e0051193183a5f987d64fcef4aa5 (patch)
treeacec1fbf80fbf96710ce2eb3fb07840e8ba3d4ea
parent7871d2a9cacf67ab1fd6704eb6be5f6bbdc39372 (diff)
doc: Fix a few typos and awkward links
-rw-r--r--doc/src/sgml/config.sgml4
-rw-r--r--doc/src/sgml/ecpg.sgml2
-rw-r--r--doc/src/sgml/high-availability.sgml2
3 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index f4f5873f442..5c580e60dfc 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -524,10 +524,10 @@ include_dir 'conf.d'
</term>
<listitem>
<para>
- Specifies the configuration file for
- <xref linkend="auth-username-maps"> user name mapping
+ Specifies the configuration file for user name mapping
(customarily called <filename>pg_ident.conf</>).
This parameter can only be set at server start.
+ See also <xref linkend="auth-username-maps">.
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index d8dd031e493..bf2cf112924 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1162,7 +1162,7 @@ EXEC SQL END DECLARE SECTION;
There are two use cases for arrays as host variables. The first
is a way to store some text string in <type>char[]</type>
or <type>VARCHAR[]</type>, as
- explained <xref linkend="ecpg-char">. The second use case is to
+ explained in <xref linkend="ecpg-char">. The second use case is to
retrieve multiple rows from a query result without using a
cursor. Without an array, to process a query result consisting
of multiple rows, it is required to use a cursor and
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 64b91b28406..6a7dde3bb63 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -207,7 +207,7 @@ protocol to make nodes agree on a serializable transactional order.
middleware. Care must also be taken that all
transactions either commit or abort on all servers, perhaps
using two-phase commit (<xref linkend="sql-prepare-transaction">
- and <xref linkend="sql-commit-prepared">.
+ and <xref linkend="sql-commit-prepared">).
<productname>Pgpool-II</> and <productname>Continuent Tungsten</>
are examples of this type of replication.
</para>