From: Stefan Kangas <stefankangas@gmail.com>
Date: Mon, 8 Jul 2024 14:43:27 +0000 (+0200)
Subject: Checkdoc fixes in `emulation/*.el`
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=941dc294f7d3a44e6ea65e68ad89810fe95d650b;p=emacs.git

Checkdoc fixes in `emulation/*.el`

* lisp/emulation/cua-base.el:
* lisp/emulation/viper-mous.el (viper-parse-mouse-key):
* lisp/emulation/viper.el (viper-major-mode-modifier-list):
Checkdoc fixes.

(cherry picked from commit 23c1ba81ddd8e5b74d0d6e17aa53e38a04f86729)
---

diff --git a/lisp/emulation/cua-base.el b/lisp/emulation/cua-base.el
index fb6a8515d9e..8b62b04c99c 100644
--- a/lisp/emulation/cua-base.el
+++ b/lisp/emulation/cua-base.el
@@ -154,7 +154,7 @@
 ;;
 ;; To start a rectangle, use [C-return] and extend it using the normal
 ;; movement keys (up, down, left, right, home, end, C-home,
-;; C-end). Once the rectangle has the desired size, you can cut or
+;; C-end).  Once the rectangle has the desired size, you can cut or
 ;; copy it using C-x and C-c (or C-w and M-w), and you can
 ;; subsequently insert it - as a rectangle - using C-v (or C-y).  So
 ;; the only new command you need to know to work with cua-mode
diff --git a/lisp/emulation/viper-mous.el b/lisp/emulation/viper-mous.el
index 322027b56c4..fb31983f1f2 100644
--- a/lisp/emulation/viper-mous.el
+++ b/lisp/emulation/viper-mous.el
@@ -456,7 +456,7 @@ bindings in the Viper manual."
 		   (if (eq 'up event-type)
 		       "mouse-3" "down-mouse-3"))
 		  (t (error
-		      "%S: invalid button number, %S" key-var key)))
+                      "%S: Invalid button number, %S" key-var key)))
 	    meta-spec
 	    (if (memq 'meta key) "M-" "")
 	    shift-spec
diff --git a/lisp/emulation/viper.el b/lisp/emulation/viper.el
index 287292a24dc..b62e11b2649 100644
--- a/lisp/emulation/viper.el
+++ b/lisp/emulation/viper.el
@@ -486,7 +486,7 @@ unless it is coming up in a wrong Viper state."
   "List specifying how to modify the various major modes to enable some Viperisms.
 The list has the structure: ((mode viper-state keymap) (mode viper-state
 keymap) ...).  If `mode' is on the list, the `keymap' will be made active (on
-the minor-mode-map-alist) in the specified viper state.
+the `minor-mode-map-alist') in the specified viper state.
 If you change this list, have to restart Emacs for the change to take effect.
 However, if you did the change through the customization widget, then Emacs
 needs to be restarted only if you deleted a triple mode-state-keymap from the