Update docs/build/identity.rs/1.3/docs/references/specifications/revo…

…cation-timeframe-2024.mdx

Co-authored-by: Eike Haß <[email protected]>

docs/build/identity.rs/1.3/docs/references/specifications/revocation-timeframe-2024.mdx

@@ -41,7 +41,7 @@ The downside of this mechanism is that the holder of a credential using `Revocat
 to update the signature - i.e. re-issue the credential - at the end of the credential's validity timeframe. Furthermore,
 given as how a credential's validity timeframe proves the validity of the credential itself, the updates made by the issuer to the credential's status -
 i.e revoking or unrevoking it - won't be reflected on the credential until the start of a new validity timeframe. For this reason,
-issuers should choose a validity timeframe's length with respect to how frequently they expect to change the credential's status;
+issuers should choose a validity timeframe length with respect to how frequently they expect to change the credential's status;
 frequent updates deems shorter validity timeframes.
 
 :::note