@@ -29,7 +29,7 @@ const MAX_EMAIL_LENGTH: u32 = 254;
2929/// the password value.
3030///
3131/// For persisting passwords in the database, and verifying passwords against
32- /// the hash, use [`PasswordHash`].
32+ /// the hash, use [`PasswordHash`](crate::auth::PasswordHash) .
3333///
3434/// # Security
3535///
@@ -40,10 +40,12 @@ const MAX_EMAIL_LENGTH: u32 = 254;
4040///
4141/// When comparing passwords, there are two recommended approaches:
4242///
43- /// 1. The most secure approach is to use [`PasswordHash::from_password`] to
44- /// create a hash from one password, and then use [`PasswordHash::verify`] to
45- /// compare it with the other password. This method uses constant-time
46- /// equality comparison, which protects against timing attacks.
43+ /// 1. The most secure approach is to use
44+ /// [`PasswordHash::from_password`](crate::auth::PasswordHash::from_password)
45+ /// to create a hash from one password, and then use
46+ /// [`PasswordHash::verify`](crate::auth::PasswordHash::verify) to compare it
47+ /// with the other password. This method uses constant-time equality
48+ /// comparison, which protects against timing attacks.
4749///
4850/// 2. An alternative is to use the [`Password::as_str`] method and compare the
4951/// strings directly. This approach uses non-constant-time comparison, which
@@ -135,9 +137,8 @@ impl From<String> for Password {
135137
136138/// A validated email address.
137139///
138- /// This is a newtype wrapper around
139- /// [`EmailAddress`](email_address::EmailAddress) that provides validation and
140- /// integration with Cot's database system. It ensures email addresses
140+ /// This is a newtype wrapper around [`EmailAddress`] that provides validation
141+ /// and integration with Cot's database system. It ensures email addresses
141142/// comply with RFC 5321/5322 standards.
142143///
143144/// # Examples
0 commit comments