2004-09-28 Marcus Brinkmann <marcus@g10code.de>

	* gpgme.texi (Passphrase Callback): Fix last change.

diff --git a/doc/ChangeLog b/doc/ChangeLog
index fba19d06d7f1d7b2d81e6b3dc52ad013a26bb5be..c87e2491872a95e4da9028c78d58c1e145683d26 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,7 @@
+2004-09-28  Marcus Brinkmann  <marcus@g10code.de>
+
+       * gpgme.texi (Passphrase Callback): Fix last change.
+
 2004-09-27  Marcus Brinkmann  <marcus@g10code.de>
 
        * gpgme.texi (Passphrase Callback): Document

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index 04a828a5dcac13dab8c9727ff1e2442d7891e9a4..f63df5203bf7c300063ced0f94a8fdfcf4478563 100644 (file)
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -2069,7 +2069,7 @@ passphrase.  It is better if the engine retrieves the passphrase from
 a trusted agent (a daemon process), rather than having each user to
 implement their own passphrase query.  Some engines do not even
 support an external passphrase callback at all, in this case the error
-code @code{GPG_ERR_NOT_SUPPORTED) is returned.
+code @code{GPG_ERR_NOT_SUPPORTED} is returned.
 
 The user can disable the use of a passphrase callback function by
 calling @code{gpgme_set_passphrase_cb} with @var{passfunc} being