summaryrefslogtreecommitdiffstats
path: root/openpgp/src/policy.rs
diff options
context:
space:
mode:
authorWiktor Kwapisiewicz <wiktor@metacode.biz>2020-05-13 12:35:46 +0200
committerWiktor Kwapisiewicz <wiktor@metacode.biz>2020-05-13 13:56:32 +0200
commit23dc8600f5c392a0df1e2a1867186c4230d986e6 (patch)
treeda95fbccbddf4326cb631297defee6332439675c /openpgp/src/policy.rs
parent06bf8c4141d83c38f6acdf1b52c2970744c3dd76 (diff)
openpgp, buffered-reader, ffi: Fix documentation warnings.
- Fix unmatched references.
Diffstat (limited to 'openpgp/src/policy.rs')
-rw-r--r--openpgp/src/policy.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/openpgp/src/policy.rs b/openpgp/src/policy.rs
index 550b68c0..259099d2 100644
--- a/openpgp/src/policy.rs
+++ b/openpgp/src/policy.rs
@@ -8,7 +8,7 @@
//! considered weak (e.g. SHA-1). When dealing with data from an
//! untrusted source, for instance, callers will often prefer to
//! ignore signatures that rely on these algorithms even though [RFC
-//! 4880] says that "[i]mplementations MUST implement SHA-1." When
+//! 4880] says that "\[i\]mplementations MUST implement SHA-1." When
//! trying to decrypt old archives, however, users probably don't want
//! to ignore keys using MD5, even though [RFC 4880] deprecates MD5.
//!
@@ -19,7 +19,7 @@
//! `StandardPolicy`'s parameters.
//!
//! When implementing the `Policy` trait, it is *essential* that the
-//! functions are [idempotent]. That is, if the same `Policy` is used
+//! functions are [pure]. That is, if the same `Policy` is used
//! to determine whether a given `Signature` is valid, it must always
//! return the same value.
//!