doc: Minor fix of the --keyserver option.

--

Unfortunately the a reflow took place.

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/dirmngr.texi b/doc/dirmngr.texi
index f5558689a..8e0979c3e 100644
--- a/doc/dirmngr.texi
+++ b/doc/dirmngr.texi
@@ -311,15 +311,15 @@ Use @var{name} as your keyserver.  This is the server that @command{gpg}
 communicates with to receive keys, send keys, and search for
 keys.  The format of the @var{name} is a URI:
 `scheme:[//]keyservername[:port]' The scheme is the type of keyserver:
-"hkp" for the HTTP (or compatible) keyservers, "ldap" for the LDAP
-keyservers, or "mailto" for the Graff email keyserver. Note that your
-particular installation of GnuPG may have other keyserver types
-available as well. Keyserver schemes are case-insensitive. After the
-keyserver name, optional keyserver configuration options may be
-provided.  These are the same as the @option{--keyserver-options} of
-@command{gpg}, but apply only to this particular keyserver.
-
-Most keyservers synchronize with each other, so there is generally no
+"hkp" for the HTTP (or compatible) keyservers or "ldap" for the LDAP
+keyservers. Note that your particular installation of GnuPG may have
+other keyserver types available as well. Keyserver schemes are
+case-insensitive. After the keyserver name, optional keyserver
+configuration options may be provided.  These are the same as the
+@option{--keyserver-options} of @command{gpg}, but apply only to this
+particular keyserver.
+
+Some keyservers synchronize with each other, so there is not always a
 need to send keys to more than one server. Some keyservers use round
 robin DNS to give a different keyserver each time you use it.