aboutsummaryrefslogtreecommitdiffstats
path: root/lang/python/doc/src/gpgme-python-howto
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--lang/python/doc/src/gpgme-python-howto6
1 files changed, 3 insertions, 3 deletions
diff --git a/lang/python/doc/src/gpgme-python-howto b/lang/python/doc/src/gpgme-python-howto
index 4ad5bc41..e12dc364 100644
--- a/lang/python/doc/src/gpgme-python-howto
+++ b/lang/python/doc/src/gpgme-python-howto
@@ -1108,7 +1108,7 @@ address can be obtained.
:CUSTOM_ID: import-hkp4py-pm1
:END:
-The following script is avalable with the rest of the examples under
+The following script is available with the rest of the examples under
the somewhat less than original name, =pmkey-import-hkp.py=.
#+BEGIN_SRC python -i
@@ -1869,7 +1869,7 @@ with open("secret_plans.txt.asc", "wb") as afile:
afile.write(ciphertext)
#+END_SRC
-If the =recipients= paramater is empty then the plaintext is encrypted
+If the =recipients= parameter is empty then the plaintext is encrypted
symmetrically. If no =passphrase= is supplied as a parameter or via a
callback registered with the =Context()= then an out-of-band prompt
for the passphrase via pinentry will be invoked.
@@ -2662,7 +2662,7 @@ Nevertheless, there are some situations where the benefits are
demonstrable. One of the better and easier examples being the one of
the early examples in this HOWTO, the [[#howto-keys-counting][key counting]] code. Running that
example as an executable Python script, =keycount.py= (available in
-the =examples/howto/= directory), will take a noticable amount of time
+the =examples/howto/= directory), will take a noticeable amount of time
to run on most systems where the public keybox or keyring contains a
few thousand public keys.