Commit: runtime(doc): minor typo fixes (#13548)

9 views
Skip to first unread message

Christian Brabandt

unread,
Nov 19, 2023, 6:30:13 PM11/19/23
to vim...@googlegroups.com
runtime(doc): minor typo fixes (#13548)

Commit: https://github.com/vim/vim/commit/aabca259fa48865e93d58b798233b19e0cb3ec7b
Author: njohnston <nickjoh...@gmail.com>
Date: Sun Nov 19 23:18:57 2023 +0000

runtime(doc): minor typo fixes (https://github.com/vim/vim/issues/13548)

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

diff --git a/runtime/doc/if_ole.txt b/runtime/doc/if_ole.txt
index 9f899ddcc..39d70a84f 100644
--- a/runtime/doc/if_ole.txt
+++ b/runtime/doc/if_ole.txt
@@ -1,4 +1,4 @@
-*if_ole.txt* For Vim version 9.0. Last change: 2022 Oct 08
+*if_ole.txt* For Vim version 9.0. Last change: 2023 Nov 19


VIM REFERENCE MANUAL by Paul Moore
@@ -59,7 +59,7 @@ Vim exposes four methods for use by clients.
SendKeys(keys) Execute a series of keys.

This method takes a single parameter, which is a string of keystrokes. These
-keystrokes are executed exactly as if they had been types in at the keyboard.
+keystrokes are executed exactly as if they had been typed in at the keyboard.
Special keys can be given using their <..> names, as for the right hand side
of a mapping. Note: Execution of the Ex "normal" command is not supported -
see below |ole-normal|.
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 77efbd63f..34290ae1e 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -1,4 +1,4 @@
-*options.txt* For Vim version 9.0. Last change: 2023 Nov 11
+*options.txt* For Vim version 9.0. Last change: 2023 Nov 19


VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1424,7 +1424,7 @@ A jump table for the options with a short description can be found at |Q_op|.
Some applications use the BOM to recognize the encoding of the file.
Often used for UCS-2 files on MS-Windows. For other applications it
causes trouble, for example: "cat file1 file2" makes the BOM of file2
- appear halfway the resulting file. Gcc doesn't accept a BOM.
+ appear halfway through the resulting file. Gcc doesn't accept a BOM.
When Vim reads a file and 'fileencodings' starts with "ucs-bom", a
check for the presence of the BOM is done and 'bomb' set accordingly.
Unless 'binary' is set, it is removed from the first line, so that you
Reply all
Reply to author
Forward
0 new messages