Commit767ce36

committed

doc: Fix a few typos and awkward links

1 parente3044f6 commit767ce36Copy full SHA for 767ce36

File tree

-8

lines changed

-8

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -878,7 +878,7 @@ SELECT pg_start_backup('label', false, false);`
`878`	`878`	`<application>pg_dump</application> or`
`879`	`879`	`<application>pg_dumpall</application>). It is neither`
`880`	`880`	`necessary nor desirable to stop normal operation of the database`
`881`		`- while you do this. See section`
	`881`	`+ while you do this. See`
`882`	`882`	`<xref linkend="backup-lowlevel-base-backup-data"> for things to`
`883`	`883`	`consider during this backup.`
`884`	`884`	`</para>`
`@@ -988,7 +988,7 @@ SELECT pg_start_backup('label', true);`
`988`	`988`	`<application>pg_dump</application> or`
`989`	`989`	`<application>pg_dumpall</application>). It is neither`
`990`	`990`	`necessary nor desirable to stop normal operation of the database`
`991`		`- while you do this. See section`
	`991`	`+ while you do this. See`
`992`	`992`	`<xref linkend="backup-lowlevel-base-backup-data"> for things to`
`993`	`993`	`consider during this backup.`
`994`	`994`	`</para>`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -532,10 +532,10 @@ include_dir 'conf.d'`
`532`	`532`	`</term>`
`533`	`533`	`<listitem>`
`534`	`534`	`<para>`
`535`		`- Specifies the configuration file for`
`536`		`- <xref linkend="auth-username-maps"> user name mapping`
	`535`	`+ Specifies the configuration file for user name mapping`
`537`	`536`	`(customarily called <filename>pg_ident.conf</>).`
`538`	`537`	`This parameter can only be set at server start.`
	`538`	`+ See also <xref linkend="auth-username-maps">.`
`539`	`539`	`</para>`
`540`	`540`	`</listitem>`
`541`	`541`	`</varlistentry>`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1189,7 +1189,7 @@ EXEC SQL END DECLARE SECTION;`
`1189`	`1189`	`There are two use cases for arrays as host variables. The first`
`1190`	`1190`	`is a way to store some text string in <type>char[]</type>`
`1191`	`1191`	`or <type>VARCHAR[]</type>, as`
`1192`		`- explained <xref linkend="ecpg-char">. The second use case is to`
	`1192`	`+ explainedin<xref linkend="ecpg-char">. The second use case is to`
`1193`	`1193`	`retrieve multiple rows from a query result without using a`
`1194`	`1194`	`cursor. Without an array, to process a query result consisting`
`1195`	`1195`	`of multiple rows, it is required to use a cursor and`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -207,7 +207,7 @@ protocol to make nodes agree on a serializable transactional order.`
`207`	`207`	`middleware. Care must also be taken that all`
`208`	`208`	`transactions either commit or abort on all servers, perhaps`
`209`	`209`	`using two-phase commit (<xref linkend="sql-prepare-transaction">`
`210`		`- and <xref linkend="sql-commit-prepared">.`
	`210`	`+ and <xref linkend="sql-commit-prepared">).`
`211`	`211`	`<productname>Pgpool-II</> and <productname>Continuent Tungsten</>`
`212`	`212`	`are examples of this type of replication.`
`213`	`213`	`</para>`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -2296,8 +2296,8 @@ The commands accepted in walsender mode are:`
`2296`	`2296`
`2297`	`2297`	`<para>`
`2298`	`2298`	`The individual protocol messages are discussed in the following`
`2299`		`- subsections. Individual messages aredescriber in`
`2300`		`- <xref linkend="protocol-logicalrep-message-formats"> section.`
	`2299`	`+ subsections. Individual messages aredescribed in`
	`2300`	`+ <xref linkend="protocol-logicalrep-message-formats">.`
`2301`	`2301`	`</para>`
`2302`	`2302`
`2303`	`2303`	`<para>`

Comments

(0)