Revert "Decrease use of the word "Emacsen" in docs"

This reverts commit 55f46cc77cb9d72fbabadb63d8aeab45c5e005e2.

Ref. https://lists.gnu.org/r/emacs-devel/2022-10/msg00016.html

2 files changed, 11 insertions, 11 deletions

diff --git a/lisp/erc/erc-compat.el b/lisp/erc/erc-compat.el
index 4a1280fe64d..8a00e711acd 100644
--- a/lisp/erc/erc-compat.el
+++ b/lisp/erc/erc-compat.el
@@ -1,6 +1,6 @@
-;;; erc-compat.el --- ERC compatibility code for old Emacs versions  -*- lexical-binding: t; -*-
+;;; erc-compat.el --- ERC compatibility code for older Emacsen  -*- lexical-binding: t; -*-
 
-;; Copyright (C) 2002-2022 Free Software Foundation, Inc.
+;; Copyright (C) 2002-2003, 2005-2022 Free Software Foundation, Inc.
 
 ;; Author: Alex Schroeder <alex@gnu.org>
 ;; Maintainer: Amin Bandali <bandali@gnu.org>, F. Jason Park <jp@neverwas.me>
diff --git a/lisp/erc/erc-log.el b/lisp/erc/erc-log.el
index 7a79754ab45..57093d3fc6c 100644
--- a/lisp/erc/erc-log.el
+++ b/lisp/erc/erc-log.el
@@ -74,21 +74,21 @@
 ;;; TODO:
 ;;
 ;; * Really, we need to lock the logfiles somehow, so that if a user
-;;   is running multiple Emacs processes and/or on the same channel as
-;;   more than one user, only one process writes to the logfile.  This
-;;   is especially needed for those logfiles with no nick in them, as
+;;   is running multiple emacsen and/or on the same channel as more
+;;   than one user, only one process writes to the logfile.  This is
+;;   especially needed for those logfiles with no nick in them, as
 ;;   these would become corrupted.
-;;   For a single Emacs process, the problem could be solved using a
+;;   For a single emacs process, the problem could be solved using a
 ;;   variable which contained the names of buffers already being
 ;;   logged.  This would require that logging be buffer-local,
 ;;   possibly not a bad thing anyway, since many people don't want to
 ;;   log the server buffer.
-;;   For multiple Emacs processes the problem is trickier.  On some
-;;   systems, on could use the function `lock-buffer' and
-;;   `unlock-buffer'.  However, file locking isn't implemented on all
-;;   platforms, for example, there is none on w32 systems.
+;;   For multiple emacsen the problem is trickier.  On some systems,
+;;   on could use the function `lock-buffer' and `unlock-buffer'.
+;;   However, file locking isn't implemented on all platforms, for
+;;   example, there is none on w32 systems.
 ;;   A third possibility might be to fake lockfiles.  However, this
-;;   might lead to problems if one Emacs crashes, as the lockfile
+;;   might lead to problems if an emacs crashes, as the lockfile
 ;;   would be left lying around.
 
 ;;; Code: