diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index 7c090ccd79..56e854b092 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -8009,7 +8009,7 @@ ttyvb   "/usr/libexec/getty Pc"         cons25  off secure</programlisting>
             kernels.</para>
 
           <para>With this option, there should be less chance of
-            synchronization problem between the mouse and the driver.
+            synchronization problems between the mouse and the driver.
             If, however, you still see the problem, click any mouse
             button while holding the mouse still to re-synchronize the
             mouse and the driver.</para>
@@ -8022,13 +8022,13 @@ ttyvb   "/usr/libexec/getty Pc"         cons25  off secure</programlisting>
             in a slightly better way and is standard in the PS/2 mouse
             driver. It should even work with GlidePoint. (As the check code
             has become a standard feature, PSM_CHECKSYNC option is not
-            available in these versions.) However, in rare case the driver
+            available in these versions.) However, in rare cases the driver
             may erroneously report synchronization problem and you may see
             the kernel message:</para>
 
           <programlisting>psmintr: out of sync (xxxx != yyyy)</programlisting>
 
-          <para>and find your mouse does not seem to work properly.</para>
+          <para>and notice that your mouse does not work properly.</para>
 
           <para>If this happens, disable the synchronization check code
             by setting the driver flags for the PS/2 mouse driver to 0x100.