Hi
Attached are documentation fixes for vim-8.2.1801.
Regards
Dominique
--
--
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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/CAON-T_g%2BNSmtCgujXZjVrP1FF1tHmBqR1PvJ%3DGwYAYuDt0hdvA%40mail.gmail.com.
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index b2b16007e..15519f840 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -3503,7 +3503,7 @@ byteidxcomp({expr}, {nr}) *byteidxcomp()*
< The first and third echo result in 3 ('e' plus composing
character is 3 bytes), the second echo results in 1 ('e' is
one byte).
- Only works different from byteidx() when 'encoding' is set to
+ Only works differently from byteidx() when 'encoding' is set to
a Unicode encoding.
Can also be used as a |method|: >
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 713f3ba3e..fe17b60e5 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -2554,7 +2554,7 @@ A jump table for the options with a short description can be found at |Q_op|.
"x" delete each combining character on its own. When it is off (the
default) the character along with its combining characters are
deleted.
- Note: When 'delcombine' is set "xx" may work different from "2x"!
+ Note: When 'delcombine' is set "xx" may work differently from "2x"!
This is useful for Arabic, Hebrew and many other languages where one
may have combining characters overtop of base characters, and want
diff --git a/runtime/doc/version8.txt b/runtime/doc/version8.txt
index 6192c237e..431b9cd47 100644
--- a/runtime/doc/version8.txt
+++ b/runtime/doc/version8.txt
@@ -48515,7 +48515,7 @@ Solution: Recognize true and false.
Files: src/eval.c, src/testdir/test_vim9_expr.vim
Patch 8.2.1205
-Problem: Vim9: && and || work different when not compiled.
+Problem: Vim9: && and || work differently when not compiled.
Solution: Keep the value.
Files: src/eval.c, src/testdir/test_vim9_expr.vim
diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index feb889dad..b2dd12e8f 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -1140,7 +1140,7 @@ Two alternatives were considered:
def Func(arg1 number, arg2 string) bool
The first is more familiar for anyone used to C or Java. The second one
-doesn't really has an advantage over the first, so let's discard the second.
+doesn't really have an advantage over the first, so let's discard the second.
Since we use type inference the type can be left out when it can be inferred
from the value. This means that after `var` we don't know if a type or a name
