formatting

README.md

@@ -60,16 +60,16 @@ On Windows, UNC paths like `//?/c:/...` or
 `//ComputerName/Share/...` are handled specially.
 
 - Patterns starting with a double-slash followed by some
-  non-slash characters will preserve their double-slash.  As a
+  non-slash characters will preserve their double-slash. As a
   result, a pattern like `//*` will match `//x`, but not `/x`.
-- Patterns staring with `//?/<drive letter>:` will *not* treat
-  the `?` as a wildcard character.  Instead, it will be treated
+- Patterns staring with `//?/<drive letter>:` will _not_ treat
+  the `?` as a wildcard character. Instead, it will be treated
   as a normal string.
 - Patterns starting with `//?/<drive letter>:/...` will match
   file paths starting with `<drive letter>:/...`, and vice versa,
-  as if the `//?/` was not present.  This behavior only is
+  as if the `//?/` was not present. This behavior only is
   present when the drive letters are a case-insensitive match to
-  one another.  The remaining portions of the path/pattern are
+  one another. The remaining portions of the path/pattern are
   compared case sensitively, unless `nocase:true` is set.
 
 Note that specifying a UNC path using `\` characters as path

changelog.md

@@ -4,18 +4,18 @@
 
 - Handle UNC paths on Windows
 
-    This adds some slightly modified behavior when a pattern or path starts
-    with `//` on Windows.
-
-    - In the case of `//?/<drive letter>:/...`, the `?` is treated as a
-      literal character, rather than a wildcard. That is, `//?/c:` will
-      _not_ match `//x/c:`.
-    - UNC patterns starting with `//?/<drive letter>:/` will match file paths
-      starting with `<drive letter>:` if the drive letters match
-      case-insensitively.
-    - File paths starting with `//?/<drive letter>:/` will match file
-      patterns starting with `<drive letter>:` if the drive letters match
-      case-insensitively.
+  This adds some slightly modified behavior when a pattern or path starts
+  with `//` on Windows.
+
+  - In the case of `//?/<drive letter>:/...`, the `?` is treated as a
+    literal character, rather than a wildcard. That is, `//?/c:` will
+    _not_ match `//x/c:`.
+  - UNC patterns starting with `//?/<drive letter>:/` will match file paths
+    starting with `<drive letter>:` if the drive letters match
+    case-insensitively.
+  - File paths starting with `//?/<drive letter>:/` will match file
+    patterns starting with `<drive letter>:` if the drive letters match
+    case-insensitively.
 
 - Add `{preserveMultipleSlashes:true}` option to suppress the
   behavior where multiple consecutive `/` characters would be