diff options
author | Eli Flanagan <eli@typedspace.com> | 2021-03-18 15:38:02 -0400 |
---|---|---|
committer | Eli Flanagan <eli@typedspace.com> | 2021-03-18 15:38:02 -0400 |
commit | 507e2a40d41622cbdd83277258af66346829ed40 (patch) | |
tree | 75c2fe1966c76aeaa006f9e1e90cbf9802bd3c46 /openpgp/src/packet/signature.rs | |
parent | f617d9c9b0b9950e975cfe28736367b7361c1c71 (diff) |
openpgp: fix a few typos in docs
Diffstat (limited to 'openpgp/src/packet/signature.rs')
-rw-r--r-- | openpgp/src/packet/signature.rs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/openpgp/src/packet/signature.rs b/openpgp/src/packet/signature.rs index 45442b5f..14fadbe9 100644 --- a/openpgp/src/packet/signature.rs +++ b/openpgp/src/packet/signature.rs @@ -49,13 +49,13 @@ //! packet is created as a side effect of parsing a signed message //! using the [`PacketParser`]. //! -//! The [`SigntaureBuilder`] can be used to create a binding +//! The [`SignatureBuilder`] can be used to create a binding //! signature, a certification, etc. The motivation for having a //! separate data structure for creating signatures is that it //! decreases the chance that a half-constructed signature is //! accidentally exported. When modifying an existing signature, you //! can use, for instance, `SignatureBuilder::from` to convert a -//! `Signtaure` into a `SigntaureBuilder`: +//! `Signature` into a `SignatureBuilder`: //! //! ``` //! use sequoia_openpgp as openpgp; @@ -107,7 +107,7 @@ //! [`Signature4`]: struct.Signature4.html //! [streaming `Signer`]: ../../serialize/stream/struct.Signer.html //! [`PacketParser`]: ../../parse/index.html -//! [`SigntaureBuilder`]: struct.SignatureBuilder.html +//! [`SignatureBuilder`]: struct.SignatureBuilder.html //! [hints]: https://tools.ietf.org/html/rfc4880#section-5.13 //! [`Signature::normalize`]: ../enum.Signature.html#method.normalize //! [`SubpacketArea`]: subpacket/struct.SubpacketArea.html |