runtime(doc): improve documentation style in editing.txt

Usually, Vim's document provides example code after explanations.
However some part of the editing.txt doesn't follow the style, therefore
this commit modifies it so that it follows the usual style.

closes: #17607

Co-authored-by: Hirohito Higashi <h.east.727@gmail.com>
Signed-off-by: mityu <mityu.mail@gmail.com>
Signed-off-by: Hirohito Higashi <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>

diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt
index dbb991e56b24535df6c3a396b25c061faa1bb01c..270cc9e246b631ebd21a7263bee00495678f05fb 100644 (file)
--- a/runtime/doc/editing.txt
+++ b/runtime/doc/editing.txt
@@ -1,4 +1,4 @@
-*editing.txt*   For Vim version 9.1.  Last change: 2025 Jun 04
+*editing.txt*   For Vim version 9.1.  Last change: 2025 Jun 25
 
 
                  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -1342,15 +1342,15 @@ b:browsefilter variable.  You would most likely set b:browsefilter in a
 filetype plugin, so that the browse dialog would contain entries related to
 the type of file you are currently editing.  Disadvantage: This makes it
 difficult to start editing a file of a different type.  To overcome this, you
-may want to add >
+can add the following as the final filter on Windows: >
 
        All Files\t(*.*)\t*\n
 <
-as the final filter on Windows or >
+Or the following on other platforms, so that the user can still access any
+desired file: >
 
        All Files\t(*)\t*\n
 <
-on other platforms, so that the user can still access any desired file.
 
 To avoid setting browsefilter when Vim does not actually support it, you can
 use has("browsefilter"): >