pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Maxim Yablokov <m.yablokov@postgrespro.ru>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Minipatch concerning tags + new spelling/punctuation patch
Date: Mon, 23 Oct 2023 12:33:03 +0300
Message-ID: <7aad518b-3e6d-47f3-9184-b1d69cb412e7@postgrespro.ru> (raw)
In-Reply-To: <ZTXF_on70-YF3KXQ@paquier.xyz>
References: <4c2a430b-32e2-44e2-aeca-03b7db6824e4@postgrespro.ru>
	<ZTN5tn9-GMkFkbhR@paquier.xyz>
	<ZTXF_on70-YF3KXQ@paquier.xyz>

Hello!

Thanks a lot!

We have also prepared a small patch concerning spelling, punctuation, 
etc. We've decided to send it separately, so it'll be easier to review. 
Please have a look.

(just in case: e.kiryanova@postgrespro.ru, e.indrupskaya@postgrespro.ru, 
o.sibiryakov@postgrespro.ru, m.yablokov@postgrespro.ru)

23.10.2023 04:01, Michael Paquier пишет:
> On Sat, Oct 21, 2023 at 04:11:50PM +0900, Michael Paquier wrote:
>> But not this one.  This could just be "WAL senders", but we also use
>> the term "walsender" in physical and logical replication areas, so a
>> plural looks OK for me here, leaving it as it is now.
> I have reverted this change, added one markup for a catalog_xmin that
> was missed, fixed a few whitespaces, and applied it on HEAD.
>
> Thanks!
> --
> Michael
-- 
Best regards,
Maxim Yablokov
Technical writer-translator
Postgres Professional <https://postgrespro.com/;

Attachments:

  [text/x-patch] spelling_punctuation.patch (5.3K, ../7aad518b-3e6d-47f3-9184-b1d69cb412e7@postgrespro.ru/3-spelling_punctuation.patch)
  download | inline diff:
diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 25febcac4c0..975b9dc9523 100644
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -1158,7 +1158,7 @@ SELECT 'w;x*y-z' = 'wxyz' COLLATE num_ignore_punct; -- true
     <para>
      <xref linkend="icu-collation-levels"/> shows which textual feature
      differences are considered significant when determining equality at the
-     given level. The unicode character <literal>U+2063</literal> is an
+     given level. The Unicode character <literal>U+2063</literal> is an
      invisible separator, and as seen in the table, is ignored for at all
      levels of comparison less than <literal>identic</literal>.
     </para>
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 73e3b39e8b4..2f1bd6fc8a7 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -984,7 +984,7 @@ mymap   /^(.*)@otherdomain\.com$   guest
    a slash (<literal>/</literal>), the remainder of the field is treated
    as a regular expression (see <xref linkend="posix-syntax-details"/>
    for details of <productname>PostgreSQL</productname>'s regular
-   expression syntax. It is not possible to use <literal>\1</literal>
+   expression syntax). It is not possible to use <literal>\1</literal>
    to use a capture from regular expression on
    <replaceable>system-username</replaceable> for a regular expression
    on <replaceable>database-username</replaceable>.
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index 8e0b2705d34..9b25e9fdb1b 100644
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -2090,9 +2090,9 @@ ninja
     configure with the <option>--backend</option> option to select the one you
     want to use and then build using <literal>meson compile</literal>. To
     learn more about these backends and other arguments you can provide to
-    ninja, you can refer to the meson <ulink
+    ninja, you can refer to the <ulink
     url="https://mesonbuild.com/Running-Meson.html#building-from-the-source">
-    documentation</ulink>.
+    Meson documentation</ulink>.
    </para>
   </step>
 
diff --git a/doc/src/sgml/nls.sgml b/doc/src/sgml/nls.sgml
index 9b6a7da870d..0ad1b2c9c45 100644
--- a/doc/src/sgml/nls.sgml
+++ b/doc/src/sgml/nls.sgml
@@ -205,7 +205,7 @@ make update-po
    <para>
     The PO files can be edited with a regular text editor. There are also
     several specialized editors for PO files which can help the process with
-    translation specific features.
+    translation-specific features.
     There is (unsurprisingly) a PO mode for Emacs, which can be quite
     useful.
    </para>
diff --git a/doc/src/sgml/pgwalinspect.sgml b/doc/src/sgml/pgwalinspect.sgml
index 762ad698176..3a8121c70f1 100644
--- a/doc/src/sgml/pgwalinspect.sgml
+++ b/doc/src/sgml/pgwalinspect.sgml
@@ -209,7 +209,7 @@ block_fpi_data    |
       <para>
        The <function>pg_filenode_relation</function> function (see
        <xref linkend="functions-admin-dblocation"/>) can help you to
-       determine which relation was modified during original execution
+       determine which relation was modified during original execution.
       </para>
      </tip>
      <para>
diff --git a/doc/src/sgml/ref/create_foreign_table.sgml b/doc/src/sgml/ref/create_foreign_table.sgml
index ae1f94b9de7..dc4b9075990 100644
--- a/doc/src/sgml/ref/create_foreign_table.sgml
+++ b/doc/src/sgml/ref/create_foreign_table.sgml
@@ -376,7 +376,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
     an <command>UPDATE</command> that changes the partition key value can
     cause a row to be moved from a local partition to a foreign-table
     partition, provided the foreign data wrapper supports tuple routing.
-    However it is not currently possible to move a row from a
+    However, it is not currently possible to move a row from a
     foreign-table partition to another partition.
     An <command>UPDATE</command> that would require doing that will fail
     due to the partitioning constraint, assuming that that is properly
diff --git a/doc/src/sgml/system-views.sgml b/doc/src/sgml/system-views.sgml
index 2b35c2f91b3..970b3bd44b0 100644
--- a/doc/src/sgml/system-views.sgml
+++ b/doc/src/sgml/system-views.sgml
@@ -1608,7 +1608,7 @@
 
   <para>
    Apply transaction locks are used in parallel mode to apply the transaction
-   in logical replication. The remote transaction id is displayed in the
+   in logical replication. The remote transaction ID is displayed in the
    <structfield>transactionid</structfield> column. The <structfield>objsubid</structfield>
    displays the lock subtype which is 0 for the lock used to synchronize the
    set of changes, and 1 for the lock used to wait for the transaction to
diff --git a/doc/src/sgml/xact.sgml b/doc/src/sgml/xact.sgml
index 1813cd07748..0f768a23a69 100644
--- a/doc/src/sgml/xact.sgml
+++ b/doc/src/sgml/xact.sgml
@@ -156,7 +156,7 @@
   <para>
    When a top-level transaction with an xid commits, all of its
    subcommitted child subtransactions are also persistently recorded
-   as committed in the <filename>pg_xact</filename> directory.  If the
+   as committed in the <filename>pg_xact</filename> subdirectory.  If the
    top-level transaction aborts, all its subtransactions are also aborted,
    even if they were subcommitted.
   </para>


view thread (2+ messages)  latest in thread

Message-ID: <7aad518b-3e6d-47f3-9184-b1d69cb412e7@postgrespro.ru>
Permalink:  ../7aad518b-3e6d-47f3-9184-b1d69cb412e7@postgrespro.ru/
Also on:    postgresql.org/message-id/7aad518b-3e6d-47f3-9184-b1d69cb412e7@postgrespro.ru

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: m.yablokov@postgrespro.ru, michael@paquier.xyz, pgsql-docs@lists.postgresql.org
  Subject: Re: Minipatch concerning tags + new spelling/punctuation patch
  In-Reply-To: <7aad518b-3e6d-47f3-9184-b1d69cb412e7@postgrespro.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox