diff --git a/docs/build/identity.rs/1.3/docs/references/specifications/revocation-timeframe-2024.mdx b/docs/build/identity.rs/1.3/docs/references/specifications/revocation-timeframe-2024.mdx
index 07e3bc1c2bd..24a83822a09 100644
--- a/docs/build/identity.rs/1.3/docs/references/specifications/revocation-timeframe-2024.mdx
+++ b/docs/build/identity.rs/1.3/docs/references/specifications/revocation-timeframe-2024.mdx
@@ -33,7 +33,7 @@ the credential's index in the issuers revocation bitmap to avoid linkability.
 ### Validity Timeframe
 If the revocation index is concealed to the verifier how can it assert the validity of the presented credential?
 To solve this issue `RevocationTimeframe2024` introduces the concept of a _validity timeframe_, i.e. a limited span of time
-in which the credential is guaranted to be non-revoked. By having a validity timeframe embedded in the credential's status
+in which the credential is guaranted to be non-revoked. By having a validity timeframe embedded in the credentials status
 the verifier can prove the credential's validity by verifying the credential's signature.
 
 The downside of this mechanism is that the holder of a credential using `RevocationTimeframe2024` has to contact the credential's issuer