docs: fix invalid vimdoc #42353

13 files changed, 20 insertions, 25 deletions

diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
index 8e71804d20..86d1e796f5 100644
--- a/runtime/doc/autocmd.txt
+++ b/runtime/doc/autocmd.txt
@@ -496,7 +496,7 @@ CmdAtom				After a user action (an "atom" of input): any
 				    - "excmd": Ex cmdline session.
 				    - "insert": Insert session.
 				    - "jump": Absolute motion ("G", marks,
-				      "H", |jumplist).
+				      "H", |jumplist|).
 				    - "mapping": Composite (≥2 subatoms).
 				    - "motion": Cursor-relative motion ("w",
 				      "%", "fx", "*").
diff --git a/runtime/doc/channel.txt b/runtime/doc/channel.txt
index e35e932551..3ae49f493e 100644
--- a/runtime/doc/channel.txt
+++ b/runtime/doc/channel.txt
@@ -267,4 +267,4 @@ when output is received: >lua
     vim.cmd("startinsert")
 <
 
- vim:tw=78:ts=8:et:sw=4:ft=help:norl:
\ No newline at end of file
+ vim:tw=78:ts=8:et:sw=4:ft=help:norl:
diff --git a/runtime/doc/dev_test.txt b/runtime/doc/dev_test.txt
index 3d3290e338..461f69475c 100644
--- a/runtime/doc/dev_test.txt
+++ b/runtime/doc/dev_test.txt
@@ -512,11 +512,11 @@ Number; !must be defined to function properly):
   search inside `/.deps`. If absent, nothing is excluded.
 
 - `NVIM_TEST_CORE_DB_CMD` (FU) (S): command to get backtrace out of the
-  debugger. E.g. `gdb -n -batch -ex "thread apply all bt full"
-  "$_NVIM_TEST_APP" -c "$_NVIM_TEST_CORE"`. Defaults to the example command.
-  This debug command may use environment variables `_NVIM_TEST_APP` (path to
+  debugger. It may use environment variables `_NVIM_TEST_APP` (path to
   application which is being debugged: normally either nvim or luajit) and
-  `_NVIM_TEST_CORE` (core file to get backtrace from).
+  `_NVIM_TEST_CORE` (core file to get backtrace from). Default: >
+    gdb -n -batch -ex "thread apply all bt full" "$_NVIM_TEST_APP" -c "$_NVIM_TEST_CORE"
+<
 
 - `NVIM_TEST_CORE_RANDOM_SKIP` (FU) (D): makes `check_cores` not check cores
   after approximately 90% of the tests. Should be used when finding cores is
diff --git a/runtime/doc/motion.txt b/runtime/doc/motion.txt
index f341eaf945..588bea8d6e 100644
--- a/runtime/doc/motion.txt
+++ b/runtime/doc/motion.txt
@@ -272,7 +272,7 @@ f{char}			To [count]'th occurrence of {char} to the right.  The
 			in Insert mode can be used to switch this on/off
 			|i_CTRL-^|.
 
-			See |getcharsearch() |setcharsearch()
+			See |getcharsearch()| |setcharsearch()|
 
 							*F*
 F{char}			To the [count]'th occurrence of {char} to the left.
@@ -285,7 +285,7 @@ t{char}			Till before [count]'th occurrence of {char} to the
 			{char} |inclusive|.
 			{char} can be entered like with the |f| command.
 
-			See |getcharsearch() |setcharsearch()
+			See |getcharsearch()| |setcharsearch()|
 
 							*T*
 T{char}			Till after [count]'th occurrence of {char} to the
@@ -296,13 +296,13 @@ T{char}			Till after [count]'th occurrence of {char} to the
 							*;*
 ;			Repeat latest f, t, F or T [count] times.
 
-			See |getcharsearch() |setcharsearch() |cpo-;|
+			See |getcharsearch()| |setcharsearch()| |cpo-;|
 
 							*,*
 ,			Repeat latest f, t, F or T in opposite direction
 			[count] times.
 
-			See |getcharsearch() |setcharsearch() |cpo-;|
+			See |getcharsearch()| |setcharsearch()| |cpo-;|
 
 ==============================================================================
 3. Up-down motions					*up-down-motions*
diff --git a/runtime/doc/nvim.txt b/runtime/doc/nvim.txt
index c8044622b2..b91bf95763 100644
--- a/runtime/doc/nvim.txt
+++ b/runtime/doc/nvim.txt
@@ -106,5 +106,4 @@ the same Nvim configuration on all of your machines, by creating
     source ~/.config/nvim/init.vim
 <
 
-==============================================================================
  vim:tw=78:ts=8:et:ft=help:norl:
diff --git a/runtime/doc/pi_gzip.txt b/runtime/doc/pi_gzip.txt
index da5bba92f7..caf0f2b256 100644
--- a/runtime/doc/pi_gzip.txt
+++ b/runtime/doc/pi_gzip.txt
@@ -47,5 +47,4 @@ If you have 'patchmode' set, it will be appended after the extension for
 compression.  Thus editing the patchmode file will not give you the automatic
 decompression.  You have to rename the file if you want this.
 
-==============================================================================
  vim:tw=78:ts=8:noet:ft=help:norl:
diff --git a/runtime/doc/pi_paren.txt b/runtime/doc/pi_paren.txt
index 80498e1d10..7817a3612f 100644
--- a/runtime/doc/pi_paren.txt
+++ b/runtime/doc/pi_paren.txt
@@ -66,5 +66,4 @@ If you would like the |%| command to work better, the |matchit| plugin can be
 used.  This plugin also helps to skip matches in comments.  This is unrelated
 to the matchparen highlighting, they use a different mechanism.
 
-==============================================================================
  vim:tw=78:ts=8:noet:ft=help:norl:
diff --git a/runtime/doc/pi_tar.txt b/runtime/doc/pi_tar.txt
index 3104853852..1d77d9defe 100644
--- a/runtime/doc/pi_tar.txt
+++ b/runtime/doc/pi_tar.txt
@@ -166,5 +166,4 @@ Copyright 2005-2017:					*tar-copyright*
 				  (see michael.toren.net/code/
 				   link seems dead)
 
-==============================================================================
 vim:tw=78:ts=8:noet:ft=help
diff --git a/runtime/doc/pi_tutor.txt b/runtime/doc/pi_tutor.txt
index e5432ebf42..03e66601e5 100644
--- a/runtime/doc/pi_tutor.txt
+++ b/runtime/doc/pi_tutor.txt
@@ -41,5 +41,4 @@ to be detected by the :Tutor command.
 It is recommended to use a less formal style when writing tutorials than in
 regular documentation (unless the content requires it).
 
-=============================================================================
   vim:tw=78:ts=8:noet:ft=help:norl:
diff --git a/runtime/doc/usr_28.txt b/runtime/doc/usr_28.txt
index fa3601133b..0ff8c4435e 100644
--- a/runtime/doc/usr_28.txt
+++ b/runtime/doc/usr_28.txt
@@ -30,7 +30,7 @@ Table of contents: |usr_toc.txt|
 *28.1*	What is folding?
 
 Folding is used to show a range of lines in the buffer as a single line on the
-screen.  Like a piece of paper which is folded to make it shorter:
+screen.  Like a piece of paper which is folded to make it shorter: >
 
 	+------------------------+
 	| line 1		 |
diff --git a/runtime/doc/vimfn.txt b/runtime/doc/vimfn.txt
index 56467d5139..9caa7d8d01 100644
--- a/runtime/doc/vimfn.txt
+++ b/runtime/doc/vimfn.txt
@@ -5329,9 +5329,9 @@ id({expr})                                                                *id()*
 		`v:_null_blob` have the same `id()` with different types
 		because they are internally represented as NULL pointers.
 		`id()` returns a hexadecimal representation of the pointers to
-		the containers (i.e. like `0x994a40`), same as `printf("%p",
-		{expr})`, but it is advised against counting on the exact
-		format of the return value.
+		the containers (i.e. like `0x994a40`), same as
+		`printf("%p", {expr})`, but it is advised against counting on
+		the exact format of the return value.
 
 		It is not guaranteed that `id(no_longer_existing_container)`
 		will not be equal to some other `id()`: new containers may
diff --git a/runtime/lua/vim/_meta/vimfn.gen.lua b/runtime/lua/vim/_meta/vimfn.gen.lua
index 205bae7fb4..f0bc974c42 100644
--- a/runtime/lua/vim/_meta/vimfn.gen.lua
+++ b/runtime/lua/vim/_meta/vimfn.gen.lua
@@ -4710,9 +4710,9 @@ function vim.fn.iconv(string, from, to) end
 --- `v:_null_blob` have the same `id()` with different types
 --- because they are internally represented as NULL pointers.
 --- `id()` returns a hexadecimal representation of the pointers to
---- the containers (i.e. like `0x994a40`), same as `printf("%p",
---- {expr})`, but it is advised against counting on the exact
---- format of the return value.
+--- the containers (i.e. like `0x994a40`), same as
+--- `printf("%p", {expr})`, but it is advised against counting on
+--- the exact format of the return value.
 ---
 --- It is not guaranteed that `id(no_longer_existing_container)`
 --- will not be equal to some other `id()`: new containers may
diff --git a/src/nvim/eval.lua b/src/nvim/eval.lua
index da8a85e87f..c7e659130d 100644
--- a/src/nvim/eval.lua
+++ b/src/nvim/eval.lua
@@ -5780,9 +5780,9 @@ M.funcs = {
       `v:_null_blob` have the same `id()` with different types
       because they are internally represented as NULL pointers.
       `id()` returns a hexadecimal representation of the pointers to
-      the containers (i.e. like `0x994a40`), same as `printf("%p",
-      {expr})`, but it is advised against counting on the exact
-      format of the return value.
+      the containers (i.e. like `0x994a40`), same as
+      `printf("%p", {expr})`, but it is advised against counting on
+      the exact format of the return value.
 
       It is not guaranteed that `id(no_longer_existing_container)`
       will not be equal to some other `id()`: new containers may