docs: fix stale ref. to CryptProvider being a trait

This commit is contained in:
Daniel McCarney 2023-12-01 11:56:33 -05:00
parent cefd6c4bc6
commit d0aef3a11c
2 changed files with 8 additions and 4 deletions

View File

@ -93,9 +93,11 @@ x86, x86-64, LoongArch64, 32-bit & 64-bit Little Endian MIPS, 32-bit PowerPC (Bi
support WebAssembly.
For more information, see [the supported `ring` target platforms][ring-target-platforms].
By providing a custom implementation of the [`crate::crypto::CryptoProvider`] trait, you
By providing a custom instance of the [`crate::crypto::CryptoProvider`] struct, you
can replace all cryptography dependencies of rustls. This is a route to being portable
to a wider set of architectures and environments, or compliance requirements.
to a wider set of architectures and environments, or compliance requirements. See the
[`crate::crypto::CryptoProvider`] documentation for more details.
Specifying `default-features = false` when depending on rustls will remove the
dependency on *ring*.

View File

@ -63,9 +63,11 @@
//! support WebAssembly.
//! For more information, see [the supported `ring` target platforms][ring-target-platforms].
//!
//! By providing a custom implementation of the [`crate::crypto::CryptoProvider`] trait, you
//! By providing a custom instance of the [`crate::crypto::CryptoProvider`] struct, you
//! can replace all cryptography dependencies of rustls. This is a route to being portable
//! to a wider set of architectures and environments, or compliance requirements.
//! to a wider set of architectures and environments, or compliance requirements. See the
//! [`crate::crypto::CryptoProvider`] documentation for more details.
//!
//! Specifying `default-features = false` when depending on rustls will remove the
//! dependency on *ring*.
//!