Spelling.

git-svn-id: https://svn.r-project.org/R/trunk@88021 00db46b3-68df-0310-9c12-caf00c1e9a41

Author: hornik

doc/manual/R-admin.texi

@@ -2863,7 +2863,7 @@ not translated in any suitable catalogue, `English'@footnote{with
 Americanisms.} is used.
 
 Note that there are several implementations of the @code{libintl}
-library used to manage message translations, includong in @code{libc}
+library used to manage message translations, including in @code{libc}
 on GNU and Alpine Linux, and as part of GNU @code{gettext} usually used
 on macOS and Windows.
 @c https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap08.html#tag_08_02

src/library/base/man/gettext.Rd

@@ -132,7 +132,7 @@ Sys.setLanguage(lang, unset = "en", C.vs.en = c("msg", "warn", "silent"),
 }
 \section{Warning}{
   These functions were written assuming that environment variable
-  \env{LANGUAGE} is supported by the implemantation of \code{libintl}.
+  \env{LANGUAGE} is supported by the implementation of \code{libintl}.
   For a long time that as universally true and it is now part of the
   2024 POSIX specification.  But in 2025 it was ignored by the
   implementation in \code{musl} (one of the implementations available on

src/library/tools/man/licensetools.Rd

@@ -30,7 +30,7 @@ analyze_license(x)
   If standardizable, it extracts the individual components and where
   these give version ranges the corresponding expansions into components
   with fixed versions.  It also indicates whether the license can be
-  verified to be FOSS
+  verified to be \abbr{FOSS}
   (\url{https://en.wikipedia.org/wiki/Free_and_open-source_software})
   licenses.
 }
@@ -41,13 +41,13 @@ analyze_license(x)
   \item{is_standardizable}{a logical indicating whether the given string
     is a standardized license spec, or can be transformed to one.}
   \item{standardization}{a character string giving the standardized
-    license spec correponding to the given string if this is
+    license spec corresponding to the given string if this is
   standardizable.}
   \item{components}{the components of the standardized license spec.}
   \item{expansions}{the expansions of the components of the standardized
     license spec.}
   \item{is_verified}{a logical indicating whether the given string can
-    be verified to specify a FOSS license.}
+    be verified to specify a \abbr{FOSS} license.}
 }
 \examples{
 ## Examples from section 'Licenses' of 'Writing R Extensions':