summaryrefslogtreecommitdiff
path: root/doc/lispref
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2014-06-05 01:14:36 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2014-06-05 01:14:36 -0700
commit136c315e0be851b679a0ae0e8011ecc768e4b039 (patch)
tree9f7bbf767266b069ec4ef0d83571a5c4044eb51a /doc/lispref
parent879f52734ce965beee611e78e5cfa132e9cbb024 (diff)
downloademacs-136c315e0be851b679a0ae0e8011ecc768e4b039.tar.gz
Spelling fixes.
Diffstat (limited to 'doc/lispref')
-rw-r--r--doc/lispref/package.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/lispref/package.texi b/doc/lispref/package.texi
index cac7519671a..c92497a8ce3 100644
--- a/doc/lispref/package.texi
+++ b/doc/lispref/package.texi
@@ -353,7 +353,7 @@ for packages.) So you should ensure that your archive is
well-maintained and keep the hosting system secure.
One way to increase the security of your packages is to @dfn{sign}
-them using a crytopgraphic key. If you have generated a
+them using a cryptographic key. If you have generated a
private/public gpg key pair, you can use gpg to sign the package like
this:
@@ -373,7 +373,7 @@ When people install packages from your archive, they can use
your public key to verify the signatures.
A full explanation of these matters is outside the scope of this
-manual. For more information on crytopgraphic keys and signing,
+manual. For more information on cryptographic keys and signing,
@pxref{Top,, GnuPG, gnupg, The GNU Privacy Guard Manual}. Emacs comes
with an interface to GNU Privacy Guard, @pxref{Top,, EasyPG, epa,
Emacs EasyPG Assistant Manual}.