doc: improve NLS instruction wording

Reported-by: "Tang, Haiying"
Discussion: https://postgr.es/m/bbbccf7a3c2d436e85d45869d612fd6b@G08CNEXMBPEKD05.g08.fujitsu.local

Author: "Tang, Haiying"

Backpatch-through: 9.5

diff --git a/doc/src/sgml/nls.sgml b/doc/src/sgml/nls.sgml
index a095a1907f914cf46f794318f45360b6cb6e1185..9295f069ce571a899e3dfdcf40cc2caa922656f2 100644 (file)
--- a/doc/src/sgml/nls.sgml
+++ b/doc/src/sgml/nls.sgml
@@ -90,7 +90,7 @@ msgstr "another translated"
 
 ...
 </programlisting>
-    The msgid's are extracted from the program source.  (They need not
+    The msgid lines are extracted from the program source.  (They need not
     be, but this is the most common way.)  The msgstr lines are
     initially empty and are filled in with useful strings by the
     translator.  The strings can contain C-style escape characters and
@@ -113,7 +113,7 @@ msgstr "another translated"
     The #. style comments are extracted from the source file where the
     message is used.  Possibly the programmer has inserted information
     for the translator, such as about expected alignment.  The #:
-    comment indicates the exact location(s) where the message is used
+    comments indicate the exact locations where the message is used
     in the source.  The translator need not look at the program
     source, but can if there is doubt about the correct
     translation.  The #, comments contain flags that describe the