From: Michael Paquier Date: Mon, 2 Nov 2020 06:15:25 +0000 (+0900) Subject: Fix some grammar and typos in comments and docs X-Git-Tag: REL_12_5~19 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=bebad33420044240297e7288d4f311095bab76b9;p=thirdparty%2Fpostgresql.git Fix some grammar and typos in comments and docs The documentation fixes are backpatched down to where they apply. Author: Justin Pryzby Discussion: https://postgr.es/m/20201031020801.GD3080@telsasoft.com Backpatch-through: 9.6 --- diff --git a/doc/src/sgml/auto-explain.sgml b/doc/src/sgml/auto-explain.sgml index 3d619d4a3dd..55509050ae3 100644 --- a/doc/src/sgml/auto-explain.sgml +++ b/doc/src/sgml/auto-explain.sgml @@ -180,7 +180,7 @@ LOAD 'auto_explain'; auto_explain.log_settings controls whether information - about modified configuration options are printed when execution plan is logged. + about modified configuration options is printed when an execution plan is logged. Only options affecting query planning with value different from the built-in default value are included in the output. This parameter is off by default. Only superusers can change this setting. diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 1e60bdb6ef1..6cb074660ad 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -3913,7 +3913,7 @@ CREATE INDEX ON measurement (logdate); Normally the set of partitions established when initially defining the - table are not intended to remain static. It is common to want to + table is not intended to remain static. It is common to want to remove old partitions of data and periodically add new partitions for new data. One of the most important advantages of partitioning is precisely that it allows this otherwise painful task to be executed diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 304b58e25ca..3ccb9554877 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -72,7 +72,7 @@ PostgreSQL documentation fetched on startup by configuring or . The use of pg_rewind is not limited to failover, e.g., a standby - server can be promoted, run some write transactions, and then rewinded + server can be promoted, run some write transactions, and then rewound to become a standby again.