diff options
| author | Paul Eggert <[email protected]> | 2014-06-05 01:14:36 -0700 |
|---|---|---|
| committer | Paul Eggert <[email protected]> | 2014-06-05 01:14:36 -0700 |
| commit | 136c315e0be851b679a0ae0e8011ecc768e4b039 (patch) | |
| tree | 9f7bbf767266b069ec4ef0d83571a5c4044eb51a /doc | |
| parent | 879f52734ce965beee611e78e5cfa132e9cbb024 (diff) | |
Spelling fixes.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/emacs/package.texi | 4 | ||||
| -rw-r--r-- | doc/lispref/package.texi | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi index 9b7f541ac5..90bdafe456 100644 --- a/doc/emacs/package.texi +++ b/doc/emacs/package.texi @@ -173,7 +173,7 @@ and use only third parties that you think you can trust! @cindex package signing The maintainers of package archives can increase the trust that you can have in their packages by @dfn{signing} them. They generate a -private/public pair of crytopgraphic keys, and use the private key to +private/public pair of cryptographic keys, and use the private key to create a @dfn{signature file} for each package. With the public key, you can use the signature files to verify who created the package, and that it has not been modified. A valid signature is not a cast-iron @@ -198,7 +198,7 @@ option has the value @code{allow-unsigned}, you can still install a package that is not signed. If you use some archives that do not sign their packages, you can add them to the list @code{package-unsigned-archives}. - For more information on crytopgraphic keys and signing, + For more information on cryptographic keys and signing, @pxref{Top,, Top, gnupg, The GNU Privacy Guard Manual}. Emacs comes with an interface to GNU Privacy Guard, @pxref{Top,, EasyPG, epa, Emacs EasyPG Assistant Manual}. diff --git a/doc/lispref/package.texi b/doc/lispref/package.texi index cac7519671..c92497a8ce 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}. |