diff --git a/collects/scribblings/reference/windows-paths.scrbl b/collects/scribblings/reference/windows-paths.scrbl
index 9de92ff692..8e3cbc33ec 100644
--- a/collects/scribblings/reference/windows-paths.scrbl
+++ b/collects/scribblings/reference/windows-paths.scrbl
@@ -239,12 +239,15 @@ Windows paths are @techlink{cleanse}d as follows: In paths that start
 @litchar{\} is added in a @litchar{\\?\REL} if an extra one is
 not already present to separate up-directory indicators from literal
 path elements, and an extra @litchar{\} is similarly added after
-@litchar{\\?\RED} if an extra one is not already present. When
-@litchar{\\?\} acts as the root and the path contains, to
-additional @litchar{/}s (which might otherwise be redundant) are
-included after the root. For other paths, multiple @litchar{/}s are
-converted to single @litchar{/}s (except at the beginning of a shared
-folder name), a @litchar{/} is inserted after the colon in a drive
+@litchar{\\?\RED} if an extra one is not already present. 
+@;{>> I don't know what was meant to go in place of "???", and I can't
+figure out an example that could trigger this case: <<
+When @litchar{\\?\} acts as the drive and the path contains ???, two
+additional @litchar{\}s (which might otherwise be redundant) are
+included after the root.}@;
+For other paths, multiple @litchar{/}s and @litchar{\}s are
+converted to single @litchar{/}s or @litchar{\} (except at the beginning of a shared
+folder name), and a @litchar{\} is inserted after the colon in a drive
 specification if it is missing.
 
 For @racket[(bytes->path-element _bstr)], @litchar{/}s, colons,