If a newline appears in markdown code blocks, they are literally copied into the output. This leads to strange markup in the grep documentation where there is a line break between the command and the flag. This fixes that:

Index: www/grep.md
==================================================================
--- www/grep.md
+++ www/grep.md
@@ -18,15 +18,15 @@
 | `-l`   | list a checkin ID prefix for matching historical versions of the file
 | `-v`   | print each checkin ID considered, regardless of whether it matches
 
 That leaves many divergences at the option level from POSIX `grep`:
 
-*   There is no built-in way to get a count of matches, as with `grep
-    -c`.
+*   There is no built-in way to get a count of matches, as with
+    `grep -c`.
 
-*    You cannot give more than one pattern, as with `grep -e` or `grep
-     -f`.
+*    You cannot give more than one pattern, as with `grep -e` or
+     `grep -f`.
 
 *   There is no equivalent of `grep -F` to do literal fixed-string
     matches only.
 
 *   `fossil grep -l` does not do precisely the same thing as POSIX