Fix typos and grammar in comments and docs

Fixes: https://github.com/dotnet/runtime/pull/124003#discussion_r2789354505
Fixes: https://github.com/dotnet/runtime/pull/124003#discussion_r2789354515
Fixes: https://github.com/dotnet/runtime/pull/124003#discussion_r2820960196

diff --git a/po/Makevars b/po/Makevars
index 0d9182e40e9e70407d348a3070e57bcc63e678f8..b2d8a7cfbe00fe1b5e61b4e4a150c01cd98f7a63 100644 (file)
--- a/po/Makevars
+++ b/po/Makevars
@@ -14,7 +14,7 @@ subdir = po
 top_builddir = ..
 
 # These options get passed to xgettext.
-XGETTEXT_OPTIONS = --add-location=file --no-wrap --keyword=_ --keyword=N_ '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpret as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."'
+XGETTEXT_OPTIONS = --add-location=file --no-wrap --keyword=_ --keyword=N_ '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpreted as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."'
 
 # This is the copyright holder that gets inserted into the header of the
 # $(DOMAIN).pot file.  Set this to the copyright holder of the surrounding

diff --git a/src/common/tuklib_gettext.h b/src/common/tuklib_gettext.h
index e5ad5e6f78a1fbb32140026dd8480aba80db60f2..258156f2389de424723d45a212d0a841f83384a9 100644 (file)
--- a/src/common/tuklib_gettext.h
+++ b/src/common/tuklib_gettext.h
@@ -41,11 +41,11 @@
 #define N_(msgid) msgid
 
 // Optional: Strings that are word wrapped using tuklib_mbstr_wrap may be
-// marked with W_("foo) in the source code. xgettext can then add a comment
+// marked with W_("foo") in the source code. xgettext can then add a comment
 // to all such strings to inform translators. The following option needs to
 // be added to XGETTEXT_OPTIONS in po/Makevars or in an equivalent place:
 //
-// '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpret as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."'
+// '--keyword=W_:1,"This is word wrapped at spaces. The Unicode character U+00A0 works as a non-breaking space. Tab (\t) is interpreted as a zero-width space (the tab itself is not displayed); U+200B is NOT supported. Manual word wrapping with \n is supported but requires care."'
 //
 // NOTE: The double-quotes in the --keyword argument above must be passed to
 // xgettext as is, thus one needs the single-quotes in Makevars.

diff --git a/src/common/tuklib_mbstr_wrap.h b/src/common/tuklib_mbstr_wrap.h
index 4e2f297dabb4121edb03185505297ceea4f2fe17..a13be3a9629801d44b0637accf9b347754593108 100644 (file)
--- a/src/common/tuklib_mbstr_wrap.h
+++ b/src/common/tuklib_mbstr_wrap.h
@@ -28,10 +28,10 @@
 TUKLIB_DECLS_BEGIN
 
 /// One or more output lines exceeded right_margin.
-/// This only a warning; everything was still printed successfully.
+/// This is only a warning; everything was still printed successfully.
 #define TUKLIB_WRAP_WARN_OVERLONG   0x01
 
-/// Error writing to to the output FILE. The error flag in the FILE
+/// Error writing to the output FILE. The error flag in the FILE
 /// should have been set as well.
 #define TUKLIB_WRAP_ERR_IO          0x02
 

diff --git a/src/common/w32_application.manifest.comments.txt b/src/common/w32_application.manifest.comments.txt
index de5c2105acf95f0bb4b97fc3ade551eb8571f392..16f79ff0e085d0682f2af19461c6532c014a5a3a 100644 (file)
--- a/src/common/w32_application.manifest.comments.txt
+++ b/src/common/w32_application.manifest.comments.txt
@@ -37,7 +37,7 @@ This is useful for programs that use main():
   * UTF-8 allows such programs to access files whose names contain
     characters that don't exist in the current legacy code page.
     However, filenames on Windows may contain unpaired surrogates
-    (invalid UTF-16). Such files cannot be accesses even with the
+    (invalid UTF-16). Such files cannot be accessed even with the
     UTF-8 code page.
 
   * UTF-8 avoids a security issue in command line argument handling: