Hi,
I found a few typos in the documentation. I also rephrased a few places
that sounded unclear.
The changes can be found in the attached patch.
--
Cheers,
Lech
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
diff --git a/runtime/doc/change.txt b/runtime/doc/change.txt
index 6e53111..f40e2fc 100644
--- a/runtime/doc/change.txt
+++ b/runtime/doc/change.txt
@@ -1417,8 +1417,8 @@ Reindenting using a different method like |gq| or |=| will not consult
alignment flags either. The same behaviour can be defined in those other
formatting options. One consideration is that 'cindent' has additional options
for context based indenting of comments but cannot replicate many three piece
-indent alignments. However, 'indentexpr' is has the ability to work better
-with three piece comments.
+indent alignments. However, 'indentexpr' has the ability to work better with
+three piece comments.
Other examples: >
"b:*" Includes lines starting with "*", but not if the "*" is
diff --git a/runtime/doc/fold.txt b/runtime/doc/fold.txt
index 24a8dcb..4f27933 100644
--- a/runtime/doc/fold.txt
+++ b/runtime/doc/fold.txt
@@ -60,7 +60,7 @@ level form a fold, with the lines with a higher level forming a nested fold.
The nesting of folds is limited with 'foldnestmax'.
Some lines are ignored and get the fold level of the line above or below it,
-whatever is the lowest. These are empty or white lines and lines starting
+whichever is lower. These are empty or white lines and lines starting
with a character in 'foldignore'. White space is skipped before checking for
characters in 'foldignore'. For C use "#" to ignore preprocessor lines.
diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index 29b9e9f..0499a01 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -480,7 +480,7 @@ You can create an empty {rhs} by typing nothing after a single CTRL-V (you
have to type CTRL-V two times). Unfortunately, you cannot do this in a vimrc
file.
*<Nop>*
-A easier way to get a mapping that doesn't produce anything, is to use "<Nop>"
+An easier way to get a mapping that doesn't produce anything, is to use "<Nop>"
for the {rhs}. This only works when the |<>| notation is enabled. For
example, to make sure that function key 8 does nothing at all: >
:map <F8> <Nop>
@@ -495,7 +495,7 @@ scenario: >
:set encoding=utf-8
The mapping for <M-C> is defined with the latin1 encoding, resulting in a 0xc3
byte. If you type the character � (0xe1 <M-a>) in UTF-8 encoding this is the
-two bytes 0xc3 0xa1. You don't want the 0xc3 byte to be mapped then,
+two bytes 0xc3 0xa1. You don't want the 0xc3 byte to be mapped then or
otherwise it would be impossible to type the � character.
*<Leader>* *mapleader*
diff --git a/runtime/doc/message.txt b/runtime/doc/message.txt
index 2a5f0f5..4379c26 100644
--- a/runtime/doc/message.txt
+++ b/runtime/doc/message.txt
@@ -27,8 +27,8 @@ The "g<" command can be used to see the last page of previous command output.
This is especially useful if you accidentally typed <Space> at the hit-enter
prompt. You are then back at the hit-enter prompt and can then scroll further
back.
-Note: when you stopped the output with "q" at the more prompt only up to that
-point will be displayed.
+Note: if the output has been stopped with "q" at the more prompt, it will only
+be displayed up to this point.
The previous command output is cleared when another command produces output.
If you are using translated messages, the first printed line tells who
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index a367e06..6089b8f 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -3094,7 +3094,7 @@ A jump table for the options with a short description can be found at |Q_op|.
closed. Also for manually closed folds. With the default value of
one a fold can only be closed if it takes up two or more screen lines.
Set to zero to be able to close folds of just one screen line.
- Note that this only has an effect of what is displayed. After using
+ Note that this only has an effect on what is displayed. After using
"zc" to close a fold, which is displayed open because it's smaller
than 'foldminlines', a following "zc" may close a containing fold.
