runtime(doc): capitalize correctly

Commit: 
https://github.com/vim/vim/commit/217d3c17c6fa8d1223fa8dd39efd8c32897f9441
Author: Christian Brabandt <c...@256bit.org>
Date:   Mon Aug 5 17:36:09 2024 +0200

    runtime(doc): capitalize correctly
    
    * do not capitalize after a double colon when introducing a list
    * Capitalize a header line
    
    closes: #15433
    
    Signed-off-by: Christian Brabandt <c...@256bit.org>

diff --git a/runtime/doc/quickfix.txt b/runtime/doc/quickfix.txt
index d759c18a4..da13b4689 100644
--- a/runtime/doc/quickfix.txt
+++ b/runtime/doc/quickfix.txt
@@ -1,4 +1,4 @@
-*quickfix.txt*  For Vim version 9.1.  Last change: 2024 Jul 17
+*quickfix.txt*  For Vim version 9.1.  Last change: 2024 Aug 05
 
 
                  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -1006,7 +1006,7 @@ Another option is using 'makeencoding'.
 ==============================================================================
 5. Using :vimgrep and :grep                            *grep* *lid*
 
-Vim has two ways to find matches for a pattern: Internal and external.  The
+Vim has two ways to find matches for a pattern: internal and external.  The
 advantage of the internal grep is that it works on all systems and uses the
 powerful Vim search patterns.  An external grep program can be used when the
 Vim grep does not do what you want.
@@ -1035,7 +1035,7 @@ commands can be combined to create a NewGrep command: >
         command! -nargs=+ NewGrep execute 'silent grep! <args>' | copen 42
 
 
-5.1 using Vim's internal grep
+5.1 Using Vim's internal grep
 
                                        *:vim* *:vimgrep* *E682* *E683*
 :vim[grep][!] /{pattern}/[g][j][f] {file} ...

-- 
-- 
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 on the web visit 
https://groups.google.com/d/msgid/vim_dev/E1saztT-00GvSL-2M%40256bit.org.

Raspunde prin e-mail lui