doc: Fix full stops.

* doc/gpg-agent.texi, doc/gpg.texi, doc/gpgsm.texi,
doc/instguide.texi, doc/scdaemon.texi, doc/specify-user-id.texi,
doc/tools.texi: Fix.

doc/gpg-agent.texi

@@ -246,7 +246,7 @@ memory allocation
 @item 6  (64)
 caching
 @item 7  (128)
-show memory statistics.
+show memory statistics
 @item 9  (512)
 write hashed data to files named @code{dbgmd-000*}
 @item 10 (1024)
@@ -1202,7 +1202,7 @@ Format the fingerprint according to gpg rules for a v4 keys.
 @item @@FPR@@
 Choose an appropriate format to format the fingerprint.
 @item @@@@
-Replaced by a single @code{@@}
+Replaced by a single @code{@@}.
 @end table
 
 @node Agent GET_PASSPHRASE

doc/gpg.texi

@@ -598,7 +598,7 @@ fingerprint (preferred) or their keyid.
 @node OpenPGP Key Management
 @subsection How to manage your keys
 
-This section explains the main commands for key management
+This section explains the main commands for key management.
 
 @table @gnupgtabopt
 

doc/gpgsm.texi

@@ -703,7 +703,7 @@ memory allocation
 @item 6  (64)
 caching
 @item 7  (128)
-show memory statistics.
+show memory statistics
 @item 9  (512)
 write hashed data to files named @code{dbgmd-000*}
 @item 10 (1024)
@@ -1269,7 +1269,7 @@ The decryption is done by using the command
 @end example
 
 It performs the decrypt operation after doing some check on the internal
-state. (e.g. that all needed data has been set).  Because it utilizes
+state (e.g. that all needed data has been set).  Because it utilizes
 the GPG-Agent for the session key decryption, there is no need to ask
 the client for a protecting passphrase - GpgAgent takes care of this by
 requesting this from the user.

doc/instguide.texi

@@ -19,7 +19,7 @@ get that whole thing up and running.
 
 Building the software is described in the file @file{INSTALL}.  Given
 that you are already reading this documentation we can only give some
-extra hints
+extra hints.
 
 To comply with the rules on GNU systems you should have build time
 configured @command{gnupg} using:

doc/scdaemon.texi

@@ -176,7 +176,7 @@ memory allocation
 @item 6  (64)
 caching
 @item 7  (128)
-show memory statistics.
+show memory statistics
 @item 9  (512)
 write hashed data to files named @code{dbgmd-000*}
 @item 10 (1024)

doc/specify-user-id.texi

@@ -101,7 +101,7 @@ This is indicated by a leading slash, directly followed by the RFC-2253
 encoded DN of the subject.  Note that you can't use the string printed
 by @code{gpgsm --list-keys} because that one has been reordered and modified
 for better readability; use @option{--with-colons} to print the raw
-(but standard escaped) RFC-2253 string
+(but standard escaped) RFC-2253 string.
 
 @cartouche
 @example
@@ -132,7 +132,7 @@ RFC-2253 encoded DN of the issuer. See note above.
 @end example
 @end cartouche
 
-@item By keygrip
+@item By keygrip.
 This is indicated by an ampersand followed by the 40 hex digits of a
 keygrip.  @command{gpgsm} prints the keygrip when using the command
 @option{--dump-cert}.  It does not yet work for OpenPGP keys.

doc/tools.texi

@@ -1446,7 +1446,7 @@ string @code{true} or @code{yes}.  The evaluation is done by passing
 Run commands from @var{file}.
 
 @item /bye
-Terminate the connection and the program
+Terminate the connection and the program.
 
 @item /help
 Print a list of available control commands.