Markup fixes near some text touched with previous commit.

svn path=/head/; revision=14005

en_US.ISO8859-1/books/faq/book.sgml

@@ -11671,7 +11671,7 @@ raisechar=^^</programlisting>
             that such matters really belong on -questions;</para>
 
           <para>Three to submit PRs about it, one of which is misfiled
-            under doc and consists only of "it's dark";</para>
+            under doc and consists only of <quote>it's dark</quote>;</para>
 
           <para>One to commit an untested lightbulb which breaks
             buildworld, then back it out five minutes later;</para>
@@ -11730,8 +11730,8 @@ raisechar=^^</programlisting>
           <para>Seventy-three to complain about the SNR on -hackers and
             -chat and unsubscribe in protest;</para>
 
-          <para>Thirteen to post "unsubscribe", "How do I unsubscribe?",
-            or "Please remove me from the list", followed by the usual
+          <para>Thirteen to post <quote>unsubscribe</quote>, <quote>How do I unsubscribe?</quote>,
+            or <quote>Please remove me from the list</quote>, followed by the usual
             footer;</para>
 
           <para>One to commit a working lightbulb while everybody is too
@@ -11746,7 +11746,7 @@ raisechar=^^</programlisting>
             fairings;</para>
 
           <para>Nine (including the PR originators) to ask
-            "what is MFC?";</para>
+            <quote>what is MFC?</quote>;</para>
 
           <para>Fifty-seven to complain about the lights being out two
             weeks after the bulb has been changed.</para>
@@ -11757,7 +11757,7 @@ raisechar=^^</programlisting>
             this.</emphasis></para>
 
           <para><emphasis>And then I thought,
-            "Hang on, shouldn't there be '1 to document it.' in that list somewhere?"</emphasis></para>
+            <quote>Hang on, shouldn't there be '1 to document it.' in that list somewhere?</quote></emphasis></para>
 
           <para><emphasis>And then I was enlightened :-)</emphasis></para>
         </answer>