Standardize possessive apostrophe usage in manuals, docs, and comments

See the note in admin/notes/documentation.
Ref: https://lists.gnu.org/r/emacs-devel/2012-02/msg00649.html

14 files changed, 21 insertions, 21 deletions

diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index c56b37ce9b7..8744687a531 100644
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -589,7 +589,7 @@ The @dfn{external border} is part of the decorations supplied by the
 window manager.  It is typically used for resizing the frame with the
 mouse and is therefore not shown on ``fullboth'' and maximized frames
 (@pxref{Size Parameters}).  Its width is determined by the window
-manager and cannot be changed by Emacs' functions.
+manager and cannot be changed by Emacs's functions.
 
 External borders don't exist on text terminal frames.  For graphical
 frames, their display can be suppressed by setting the
@@ -2283,7 +2283,7 @@ it on an undecorated frame.
 If non-@code{nil}, this means that this is an @dfn{override redirect}
 frame---a frame not handled by window managers under X@.  Override
 redirect frames have no window manager decorations, can be positioned
-and resized only via Emacs' positioning and resizing functions and are
+and resized only via Emacs's positioning and resizing functions and are
 usually drawn on top of all other frames.  Setting this parameter has
 no effect on MS-Windows.
 
@@ -2780,7 +2780,7 @@ visible, even though only the selected one is actually displayed.
 @end defun
 
 @defun frame-list-z-order &optional display
-This function returns a list of Emacs' frames, in Z (stacking) order
+This function returns a list of Emacs's frames, in Z (stacking) order
 (@pxref{Raising and Lowering}).  The optional argument @var{display}
 specifies which display to poll.  @var{display} should be either a frame
 or a display name (a string).  If omitted or @code{nil}, that stands for
@@ -3157,7 +3157,7 @@ A frame on a graphical display may be @dfn{visible}, @dfn{invisible}, or
 usual manner.  If it is iconified, its contents are not displayed, but
 there is a little icon somewhere to bring the frame back into view (some
 window managers refer to this state as @dfn{minimized} rather than
-@dfn{iconified}, but from Emacs' point of view they are the same thing).
+@dfn{iconified}, but from Emacs's point of view they are the same thing).
 If a frame is invisible, it is not displayed at all.
 
 @cindex mapped frame
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index 0cf41072ec3..0131305525c 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -2059,7 +2059,7 @@ is the better way to modify a named function because it keeps track of
 the modifications, so they can be listed and undone.
 
   Modifying a named function should be reserved for
-the cases where you cannot modify Emacs' behavior in any other way.
+the cases where you cannot modify Emacs's behavior in any other way.
 If it is possible to do the same thing via a hook, that is preferable
 (@pxref{Hooks}).  If you simply want to change what a particular key
 does, it may be better to write a new command, and remap the old
diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi
index 1c5cc0e20b4..e5d552815e0 100644
--- a/doc/lispref/nonascii.texi
+++ b/doc/lispref/nonascii.texi
@@ -732,7 +732,7 @@ character, a symbol whose name is the script to which the character
 belongs, according to the Unicode Standard classification of the
 Unicode code space into script-specific blocks.  This char-table has a
 single extra slot whose value is the list of all script symbols.  Note
-that Emacs' classification of characters into scripts is not a 1-for-1
+that Emacs's classification of characters into scripts is not a 1-for-1
 reflection of the Unicode standard, e.g. there is no @samp{symbol}
 script in Unicode.
 @end defvar
diff --git a/doc/lispref/package.texi b/doc/lispref/package.texi
index eb0b4ca213c..6f7b7af12dd 100644
--- a/doc/lispref/package.texi
+++ b/doc/lispref/package.texi
@@ -133,7 +133,7 @@ file (@pxref{Init File,,, emacs, The GNU Emacs Manual}).
 @end defun
 
 @deffn Command package-initialize &optional no-activate
-This function initializes Emacs' internal record of which packages are
+This function initializes Emacs's internal record of which packages are
 installed, and then calls @code{package-activate-all}.
 
 The optional argument @var{no-activate}, if non-@code{nil}, causes
diff --git a/doc/lispref/parsing.texi b/doc/lispref/parsing.texi
index 21e14b4632c..8f3c2b4a366 100644
--- a/doc/lispref/parsing.texi
+++ b/doc/lispref/parsing.texi
@@ -2159,7 +2159,7 @@ node is a defun node but doesn't have a name, or the node is
 @node Tree-sitter C API
 @section Tree-sitter C API Correspondence
 
-Emacs' tree-sitter integration doesn't expose every feature
+Emacs's tree-sitter integration doesn't expose every feature
 provided by tree-sitter's C API@.  Missing features include:
 
 @itemize
diff --git a/doc/lispref/searching.texi b/doc/lispref/searching.texi
index 7cefd581afb..7b4a9100e77 100644
--- a/doc/lispref/searching.texi
+++ b/doc/lispref/searching.texi
@@ -1977,7 +1977,7 @@ To help diagnose problems in your regexps or in the regexp engine
 itself, this function returns a string describing the compiled
 form of @var{regexp}.  To make sense of it, it can be necessary
 to read at least the description of the @code{re_opcode_t} type in the
-@code{src/regex-emacs.c} file in Emacs' source code.
+@code{src/regex-emacs.c} file in Emacs's source code.
 
 It is currently able to give a meaningful description only if Emacs
 was compiled with @code{--enable-checking}.
diff --git a/doc/misc/efaq-w32.texi b/doc/misc/efaq-w32.texi
index 411450cdc42..9ee5b679fed 100644
--- a/doc/misc/efaq-w32.texi
+++ b/doc/misc/efaq-w32.texi
@@ -2218,7 +2218,7 @@ outdated.  Tools available here that are useful for Emacs include:
 @item OpenSSL - used by @code{gnus} to talk to servers over SSL.
 @item Patch - used by @code{ediff-patch-file} and others to apply patches.
 @item Tar - used by @code{tar-mode} to edit tar files.
-@item TexInfo - used to build Emacs' manuals.
+@item TexInfo - used to build Emacs's manuals.
 @item Unzip - used by @code{archive-mode} for extracting zip files.
 @item Xpm - library to support XPM images (bundled with Emacs binaries)
 @item Zip - used by @code{archive-mode} for editing zip files.
@@ -2245,7 +2245,7 @@ image libraries that it provides, even if they are not on the
 @findex man
 
 Man pages for Emacs and other ported programs that you have can be
-read using Emacs' built-in manual reader @code{woman}.  This
+read using Emacs's built-in manual reader @code{woman}.  This
 requires no external programs, but if you do have a port of
 @command{man}, there is also an Emacs wrapper @code{man} that
 which may be slightly faster.  A Windows version of @command{man} is
diff --git a/doc/misc/erc.texi b/doc/misc/erc.texi
index 858e1ba34dc..33f35d9b5c6 100644
--- a/doc/misc/erc.texi
+++ b/doc/misc/erc.texi
@@ -2127,7 +2127,7 @@ to IRC, and don't forget that you can roll back to the previous
 version by running @kbd{M-x package-delete @key{RET}}.
 @xref{Packages,,,emacs, The Emacs Editor}, for more information.
 
-Note that a bug affecting Emacs' packaging machinery may prevent the
+Note that a bug affecting Emacs's packaging machinery may prevent the
 above method from working on Emacs versions 29 and below.  Users on 29
 can try running @kbd{C-u M-x package-install @key{RET}} instead.
 Users on 28 and below can click on the @emph{installed} @samp{erc}
diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
index f4c87bd64dd..dbe4da29d54 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -12075,7 +12075,7 @@ article buffer.  There are many methods for doing that, but two of
 them are kind of default methods.
 
 If your Emacs copy has been built with libxml2 support, then Gnus uses
-Emacs' built-in, plain elisp Simple HTML Renderer @code{shr}
+Emacs's built-in, plain elisp Simple HTML Renderer @code{shr}
 @footnote{@code{shr} displays colors as declared in the @acronym{HTML}
 article but tries to adjust them in order to be readable.  If you
 prefer more contrast, @xref{FAQ 4-16}.} which is also used by Emacs'
diff --git a/doc/misc/modus-themes.org b/doc/misc/modus-themes.org
index 20fa93c6dbc..70ba8cdc02f 100644
--- a/doc/misc/modus-themes.org
+++ b/doc/misc/modus-themes.org
@@ -144,7 +144,7 @@ and covers everything that goes into every tagged release of the themes.
 :end:
 
 The Modus themes are distributed with Emacs starting with version 28.1.
-On older versions of Emacs, they can be installed using Emacs' package
+On older versions of Emacs, they can be installed using Emacs's package
 manager or manually from their code repository.  There also exist
 packages for distributions of GNU/Linux.
 
@@ -4769,7 +4769,7 @@ and/or mode line setup.
 :custom_id: h:4cc767dc-ffef-4c5c-9f10-82eb7b8921bf
 :end:
 
-Emacs' HTML rendering library ({{{file(shr.el)}}}) may need explicit
+Emacs's HTML rendering library ({{{file(shr.el)}}}) may need explicit
 configuration to respect the theme's colors instead of whatever
 specifications the webpage provides.
 
diff --git a/doc/misc/org.org b/doc/misc/org.org
index dc7d8ef166f..dcc1ddc7f44 100644
--- a/doc/misc/org.org
+++ b/doc/misc/org.org
@@ -3359,7 +3359,7 @@ Here is the full set of built-in link types:
 
 - =gnus=, =rmail=, =mhe= ::
 
-  Link to messages or folders from a given Emacs' MUA.
+  Link to messages or folders from a given Emacs MUA.
 
 - =help= ::
 
@@ -23201,7 +23201,7 @@ than 30 stars.  This is a hard-coded limitation of ~lmax~ in
 2003, not the beginning of time.
 
 [fn:29] On computers using macOS, idleness is based on actual user
-idleness, not just Emacs' idle time.  For X11, you can install a
+idleness, not just Emacs's idle time.  For X11, you can install a
 utility program =x11idle.c=, available in the =org-contrib/=
 repository, or install the xprintidle package and set it to the
 variable ~org-clock-x11idle-program-name~ if you are running Debian,
diff --git a/doc/misc/transient.texi b/doc/misc/transient.texi
index 7419ce39206..10e4c9deef1 100644
--- a/doc/misc/transient.texi
+++ b/doc/misc/transient.texi
@@ -1458,7 +1458,7 @@ When returning to the command-loop after calling the suffix command,
 the arguments are reset to @code{nil} (which causes the function to return
 @code{nil} too).
 
-Like for Emacs' prefix arguments, it is advisable, but not mandatory,
+Like for Emacs's prefix arguments, it is advisable, but not mandatory,
 to access the infix arguments inside the command's @code{interactive} form.
 The preferred way of doing that is to call the @code{transient-args}
 function, which for infix arguments serves about the same purpose as
diff --git a/doc/misc/use-package.texi b/doc/misc/use-package.texi
index 9e11b349f20..da3deb081d9 100644
--- a/doc/misc/use-package.texi
+++ b/doc/misc/use-package.texi
@@ -575,7 +575,7 @@ add @code{:demand t} to those declarations.
 Some users want to put all their customizations in use-package
 declarations, even for variables, hooks, and options that are always
 available, without loading any package.@footnote{In other words, they
-are either preloaded in Emacs or defined in Emacs' C sources.}
+are either preloaded in Emacs or defined in Emacs's C sources.}
 
 For that purpose, you can use the no-op @samp{emacs} package:
 
@@ -640,7 +640,7 @@ simply use @code{:if} and the appropriate Lisp expression.
 @node Manual installation
 @section Manually installed package
 
-When installing packages manually, without Emacs' built-in package
+When installing packages manually, without Emacs's built-in package
 manager (@file{package.el}), it will obviously not help you set up
 autoloads or add it to your @code{load-path}.  You must do it
 yourself.  However, use-package makes this more convenient.
diff --git a/doc/misc/wisent.texi b/doc/misc/wisent.texi
index d42fe09240a..ad59ce03a4a 100644
--- a/doc/misc/wisent.texi
+++ b/doc/misc/wisent.texi
@@ -1800,7 +1800,7 @@ But @samp{rules} part is parsed in Bison style!  Why?
 Rule delimiters are the colon (@code{:}), that follows the nonterminal
 name, and a final semicolon (@code{;}).  Unfortunately these
 delimiters are not @code{open-paren}/@code{close-paren} type, and the
-Emacs' syntactic analyzer can't easily isolate data between them to
+Emacs syntactic analyzer can't easily isolate data between them to
 produce a @samp{RULES_PART} parenthesis-block-like lexical token.
 Consequently it is not possible to use @code{EXPANDFULL} to iterate in
 @samp{RULES_PART}, like this: