summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHeiko <heiko@schaefer.name>2021-03-30 11:28:09 +0200
committerHeiko <heiko@schaefer.name>2021-03-30 11:28:27 +0200
commit4ccb927639dfbdc47f1cd229b5400282e6c77421 (patch)
tree77e089d0bf8845e432195cbc7035153b14718940
parentea3690c6aa5a9b5b28ae2d6e792608d761bb973b (diff)
Minor edits in documentation.
-rw-r--r--openpgp/src/cert/amalgamation/key.rs4
-rw-r--r--openpgp/src/types/mod.rs2
2 files changed, 3 insertions, 3 deletions
diff --git a/openpgp/src/cert/amalgamation/key.rs b/openpgp/src/cert/amalgamation/key.rs
index 5962ea4b..40c0fa33 100644
--- a/openpgp/src/cert/amalgamation/key.rs
+++ b/openpgp/src/cert/amalgamation/key.rs
@@ -71,7 +71,7 @@
//! # Selecting Keys
//!
//! It is essential to choose the right keys, and to make sure that
-//! they appropriate. Below, we present some guidelines for the most
+//! they are appropriate. Below, we present some guidelines for the most
//! common situations.
//!
//! ## Encrypting and Signing Messages
@@ -190,7 +190,7 @@
//!
//! ## Decrypting a Message
//!
-//! When decrypting a message, it seems like one ought to only keys
+//! When decrypting a message, it seems like one ought to only use keys
//! that were alive, not revoked, and encryption-capable when the
//! message was encrypted. Unfortunately, we don't know when a
//! message was encrypted. But anyway, due to the slow propagation of
diff --git a/openpgp/src/types/mod.rs b/openpgp/src/types/mod.rs
index 4908f681..12ba45c2 100644
--- a/openpgp/src/types/mod.rs
+++ b/openpgp/src/types/mod.rs
@@ -29,7 +29,7 @@
//!
//! Describes a key that has been designated to issue revocation signatures.
//!
-//! # `ServerPreferences`
+//! # `KeyServerPreferences`
//!
//! Describes preferences regarding to key servers.
//!