Minor state_analyzer manpage corrections

Done according to adeason's comments on http://gerrit.openafs.org/#change,1655

Change-Id: Ia5b28473fa37ad2a877a5a56b1b7f1c4893e8db1
Reviewed-on: http://gerrit.openafs.org/1666
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>

diff --git a/doc/man-pages/pod8/state_analyzer.pod b/doc/man-pages/pod8/state_analyzer.pod
index 5f8598c..9e0f9c6 100644 (file)
--- a/doc/man-pages/pod8/state_analyzer.pod
+++ b/doc/man-pages/pod8/state_analyzer.pod
@@ -7,25 +7,25 @@ state_analyzer - Explores and queries the fileserver state database interactivel
 =for html
 <div class="synopsis">
 
-B<state_analyzer> S<<< <F<state dump file>> | B<-h> >>>
+B<state_analyzer> S<<< [F<state dump file> | B<-h>] >>>
 
 =for html
 </div>
 
 =head1 DESCRIPTION
 
-Demand-attach file server makes host / callback information
+The demand-attach file server makes host / callback information
 persistent. On shutdown, the state is saved to database L<fsstate.dat(5)>.
 On startup, the state is read, verified and restored.
 This allows for file server shutdowns or restarts without breaking
-the callbacks (an operation that could otherwise take a long time).
+all callbacks (an operation that could otherwise take a long time).
 
 B<state_analyzer> interactively explores and queries the saved
 state database, L<fsstate.dat(5)>.
 
 This command is only supported on the demand-attach file server.
 It operates at an extremely low-level and hence requires detailed
-knowledge of the OpenAFS architecture and code. 
+knowledge of the OpenAFS architecture and code.
 
 =head1 COMMANDS