Commit: runtime(doc): use codepoint consistently

[Christian Brabandt]

runtime(doc): use codepoint consistently

Commit: https://github.com/vim/vim/commit/93d9d196ed3a70174ba5e790d9e36e0478e84a09
Author: Christian Brabandt <c...@256bit.org>
Date: Wed Dec 17 23:24:57 2025 +0100

runtime(doc): use codepoint consistently

fixes: https://github.com/vim/vim/issues/18944

Signed-off-by: Christian Brabandt <c...@256bit.org>

diff --git a/runtime/doc/mbyte.txt b/runtime/doc/mbyte.txt
index 1bbc14682..9c99f22c4 100644
--- a/runtime/doc/mbyte.txt
+++ b/runtime/doc/mbyte.txt
@@ -1,4 +1,4 @@
-*mbyte.txt* For Vim version 9.1. Last change: 2025 Nov 09
+*mbyte.txt* For Vim version 9.1. Last change: 2025 Dec 17


VIM REFERENCE MANUAL by Bram Moolenaar et al.
@@ -601,7 +601,7 @@ Each field means:
- AVE: AVERAGE_WIDTH field. Ten times average width in pixels.
- CR: CHARSET_REGISTRY field. The name of the charset group.
- CE: CHARSET_ENCODING field. The rest of the charset name. For some
- charsets, such as JIS X 0208, if this field is 0, code points has
+ charsets, such as JIS X 0208, if this field is 0, codepoints has
the same value as GL, and GR if 1.

For example, in case of a 16 dots font corresponding to JIS X 0208, it is
diff --git a/runtime/doc/print.txt b/runtime/doc/print.txt
index 30c498064..133ff307d 100644
--- a/runtime/doc/print.txt
+++ b/runtime/doc/print.txt
@@ -1,4 +1,4 @@
-*print.txt* For Vim version 9.1. Last change: 2025 Nov 09
+*print.txt* For Vim version 9.1. Last change: 2025 Dec 17


VIM REFERENCE MANUAL by Bram Moolenaar
@@ -304,7 +304,7 @@ another font will be used as follows:
if o: is missing, then use b:

Some CJK fonts do not contain characters for codes in the ASCII code range.
-Also, some characters in the CJK ASCII code ranges differ in a few code points
+Also, some characters in the CJK ASCII code ranges differ in a few codepoints
from traditional ASCII characters. There are two additional fields to control
printing of characters in the ASCII code range.