Proof read the FAQ

1. killall gpsd before starting gpsmon
2. Android gpsd paragraph

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

1 files changed, 8 insertions, 6 deletions

diff --git a/www/faq.html.in b/www/faq.html.in
index 5329d7c9..215ce1ca 100644
--- a/www/faq.html.in
+++ b/www/faq.html.in
@@ -165,8 +165,10 @@ because the hotplug system will have done it for you.  You should be
 able to start a test client (such as <code>cgps</code> or <code>xgps</code>)
 and watch it report fixes.</p>
 
-<p>5. If your test client fails to run, a good test to try is to run
-<code>gpsmon</code> on the device (give it the device path as an
+<p>5. If your test client fails to run, a good test to try is to,
+after stopping any instances of gpsd that are running
+(eg, <code>killall gpsd</code> ),
+run <code>gpsmon</code> on the device (give it the device path as an
 argument). If yours reports no data at all, you probably have some
 low-level system problem with serial or USB that you'll need to fix
 before <code>gpsd</code> will operate.</p>
@@ -228,10 +230,10 @@ due to a GPSD bug or design error.</p>
 
 <p>You probably have a badly-written or buggy app installed that is
 running in background, keeping gpsd awake by keeping a client session
-to it constantly open; this can happen if the app is using "Detailed
-Localization" rather than computing its location the cheaper way using
-cell-tower signal strengths.  What you need to do is identify that app
-and remove it.</p>
+to it constantly open; this can happen if the app is using "Fine
+Location" rather than computing its location the cheaper way using
+cell-tower signal strengths ("Coarse Location").  What you need to
+do is identify that app, and decide if you wish to remove it.</p>
 
 <p>See <a href="http://www.bitdirect.nl/?p=47">this blog post</a> for
 a procedure for hunting down the bad app. In this particular case it