runtime(doc): Tweak documentation style

Commit: 
https://github.com/vim/vim/commit/5711d768181c3b08869ac41ee947a56a26763450
Author: Hirohito Higashi <h.east....@gmail.com>
Date:   Tue Jul 22 19:01:17 2025 +0200

    runtime(doc): Tweak documentation style
    
    closes: https://github.com/vim/vim/issues/17824
    
    Signed-off-by: Hirohito Higashi <h.east....@gmail.com>
    Signed-off-by: Christian Brabandt <c...@256bit.org>

diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index c7d3b401f..0eb82b9e1 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -1,4 +1,4 @@
-*builtin.txt*  For Vim version 9.1.  Last change: 2025 Jul 21
+*builtin.txt*  For Vim version 9.1.  Last change: 2025 Jul 22
 
 
                  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -12344,7 +12344,7 @@ wildtrigger()                                           
*wildtrigger()*
                produce a beep when no matches are found and generally
                operates more quietly.  This makes it suitable for triggering
                completion automatically, such as from an |:autocmd|.
-                                                       *cmdline-autocompletion*
+                                               *cmdline-autocompletion*
                Example: To make the completion menu pop up automatically as
                you type on the command line, use: >
                        autocmd CmdlineChanged [:/?] call wildtrigger()
diff --git a/runtime/doc/develop.txt b/runtime/doc/develop.txt
index 9fae2692f..9b2e21b5d 100644
--- a/runtime/doc/develop.txt
+++ b/runtime/doc/develop.txt
@@ -1,4 +1,4 @@
-*develop.txt*   For Vim version 9.1.  Last change: 2025 Jul 21
+*develop.txt*   For Vim version 9.1.  Last change: 2025 Jul 22
 
 
                  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -297,16 +297,16 @@ count.
 ==============================================================================
 3. Assumptions                                         *design-assumptions*
 
-The following sections define the portability and compatibility constraints 
that
-all Vim code and build tools must adhere to.
+The following sections define the portability and compatibility constraints
+that all Vim code and build tools must adhere to.
 
 
 MAKEFILES                                      *assumptions-makefiles*
                                                *POSIX.1-2001*
 
-Vim’s main Makefiles target maximum portability, relying solely on features
-defined in POSIX.1-2001 `make` and ignoring later POSIX standards or
-GNU/BSD extensions.  In practical terms, avoid:
+Vim's main Makefiles target maximum portability, relying solely on features
+defined in POSIX.1-2001 `make` and ignoring later POSIX standards or GNU/BSD
+extensions.  In practical terms, avoid:
 
        – % pattern rules
        – modern assignment (`:=`, `::=`) outside POSIX.1-2001
@@ -314,19 +314,18 @@ GNU/BSD extensions.  In practical terms, avoid:
        – order-only prerequisites (`|`) or automatic directory creation
        – GNU/BSD conditionals (`ifdef`, `ifndef`, `.for`/`.endfor`, …)
 
-Since POSIX.1-2001 supports only traditional suffix rules, every object
-built in a separate directory must have an explicit rule.  For example:
+Since POSIX.1-2001 supports only traditional suffix rules, every object built
+in a separate directory must have an explicit rule.  For example:
 
        objects/evalbuffer.o: evalbuffer.c
                $(CCC) -o $@ evalbuffer.c
 
-This verbosity ensures that the same Makefile builds Vim unchanged with
-the default `make` on Linux, *BSD, macOS, Solaris, AIX, HP-UX and virtually
-any Unix-like OS.
+This verbosity ensures that the same Makefile builds Vim unchanged with the
+default `make` on Linux, *BSD, macOS, Solaris, AIX, HP-UX and virtually any
+Unix-like OS.
 
-Some platform-specific Makefiles (e.g., for Windows, NSIS, or Cygwin) may
-use more advanced features when compatibility with basic make is not
-required.
+Some platform-specific Makefiles (e.g., for Windows, NSIS, or Cygwin) may use
+more advanced features when compatibility with basic make is not required.
 
 
 C COMPILER                                     *assumptions-C-compiler*
@@ -343,8 +342,8 @@ In addition, the following two `C99` features are 
explicitly allowed:
        – `//` comments, as required by |style-comments|;
        – the `_Bool` type.
 
-Platform-specific code may use any newer compiler features supported on
-that platform.
+Platform-specific code may use any newer compiler features supported on that
+platform.
 
 
 SIZE OF VARIABLES                              *assumptions-variables*
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index 522c03379..f0c380d6e 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -1,4 +1,4 @@
-*eval.txt*     For Vim version 9.1.  Last change: 2025 Jul 20
+*eval.txt*     For Vim version 9.1.  Last change: 2025 Jul 22
 
 
                  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -3312,7 +3312,7 @@ text...
                                CODE
 <
                                                                *E121*
-:let {var-name}        ..      List the value of variable {var-name}.  Multiple
+:let {var-name}        ...     List the value of variable {var-name}.  Multiple
                        variable names may be given.  Special names recognized
                        here:                           *E738*
                          g:    global variables

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/vim_dev/E1ueGa0-003yUd-22%40256bit.org.

Raspunde prin e-mail lui