Spelling and markup.

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

doc/NEWS.Rd

@@ -291,8 +291,9 @@
       \code{XLENGTH_EX}, and \code{XTRUELENGTH}.
 
       \item Enable defining \env{R_NO_REMAP_RMATH} and calling
-      \code{Rf_*()} as has been documented in WRE for a while, fixing
-      \PR{18800} thanks to \I{Mikael Jagan} and \I{Suharto Anggono}.
+      \code{Rf_*()} as has been documented in
+      \sQuote{Writing R Extensions} for a while, fixing \PR{18800}
+      thanks to \I{Mikael Jagan} and \I{Suharto Anggono}.
     }
   }
 
@@ -304,7 +305,7 @@
       variable \env{_R_CXX_USE_NO_REMAP_} to a false value (but that will
       be removed in the near future).
 
-      `Writing R Extensions' has been revised to describe the remapped
+      \sQuote{Writing R Extensions} has been revised to describe the remapped
       entry points, for with the \code{Rf_} prefix remains optional when
       used from C code (but is recommended for new C code).
 
@@ -497,7 +498,7 @@
        \item Some invalid C-level memory accesses are avoided for
        \code{loglin(, margin = NULL)}.
 
-       \code{loglin(, param = TRUE)} no longer gives an eror in corner
+       \code{loglin(, param = TRUE)} no longer gives an error in corner
        cases such as a one-dimensional input.
 
        \item \code{dev.capabilities() $ events} now reports \code{"Idle"} if

doc/manual/R-exts.texi

@@ -6058,9 +6058,9 @@ and often @acronym{CRAN} submissions attempt to use @file{endian.h}.
 The latter is a @code{glibc} extension: some OSes have
 @file{machine/endian.h} or @file{sys/endian.h} but some have neither.
 @c macOS has machine/endian.h.  Solaris had none.
-Header @file{execinfo.h} is only available on a few OSes: formwrly nor
-in MacOS nor Solaris, and currently not on Linux systems (such as Aloine
-Linux)using @code{musl}.  Nor is header @file{fpu_control.h} avaialble
+Header @file{execinfo.h} is only available on a few OSes: formerly nor
+in MacOS nor Solaris, and currently not on Linux systems (such as Alpine
+Linux) using @code{musl}.  Nor is header @file{fpu_control.h} available
 on macOS nor @code{musl}.
 
 @item
@@ -9939,9 +9939,9 @@ of reports have been of `heap-use-after-free' errors in the X11
 libraries called from Tcl/Tk.
 
 Apple provide a version of the address sanitizer in recent versions of
-its C/C++ compiler.  This will proably give messages about
-`malloc: nano zone abandoned' which are innocuous and can be suppressed
-by setting environmant variable @env{MallocNanoZone} to @code{0}.
+its C/C++ compiler.  This will probably give messages about
+@I{`malloc: nano zone abandoned'} which are innocuous and can be suppressed
+by setting environment variable @env{MallocNanoZone} to @code{0}.
 @c https://stackoverflow.com/questions/64126942/malloc-nano-zone-abandoned-due-to-inability-to-preallocate-reserved-vm-space
 
 @c 1-item menu: kept to avoid spurious warning from makeinfo 6.8/7.0
@@ -9964,7 +9964,7 @@ variable
 ASAN_OPTIONS='detect_leaks=1'
 @end example
 @noindent
-However, this was made the default as from LLVM @command{clang} 3.5 and
+However, this was made the default as from @I{LLVM} @command{clang} 3.5 and
 @command{gcc} 5.1.0.
 
 When @abbr{LSan} is enabled, leaks give the process a failure error status (by
@@ -10123,8 +10123,8 @@ For more details on the topic see
 It may or may not be possible to build @R{} itself with
 @option{-fsanitize=undefined}: problems have in the past been seen with
 @abbr{OpenMP}-using code with @command{gcc} but there has been success
-with LLVM @command{clang} up to version 16..  However, problems have been
-seen with LLVM @command{clang} 17 and later, including missing entry points
+with @I{LLVM} @command{clang} up to version 16..  However, problems have been
+seen with @I{LLVM} @command{clang} 17 and later, including missing entry points
 and @R{} builds hanging.  What has succeeded is to use @abbr{UBSAN} just for
 the package under test (and not in combination with @abbr{ASAN}).  To do so,
 check with an unaltered @R{}, using a custom @file{Makevars} file
@@ -10153,7 +10153,6 @@ the paths used, have changed several times recently.
 Apple provides a version of the undefined behaviour sanitizer in recent
 versions of its C/C++ compiler.  @R{} was built with Apple
 @command{clang} 16 with @file{config.site} containing
-@noindent
 @example
 CC="clang -fsanitize=address,undefined"
 CXX="clang++ -fsanitize=address,undefined"
@@ -10164,7 +10163,7 @@ and passed its checks.
 @node Other analyses with `clang'
 @subsection Other analyses with `clang'
 
-Recent versions of LLVM @command{clang} on Linux have
+Recent versions of @I{LLVM} @command{clang} on Linux have
 `@I{ThreadSanitizer}'
 (@uref{https://github.com/google/sanitizers/wiki#threadsanitizer}), a
 `data race detector for C/C++ programs', and `@I{MemorySanitizer}'