Apply suggestion from @yaronf

Co-authored-by: Yaron Sheffer <yaronf.ietf@gmail.com>

Author: selfissued

draft-ietf-oauth-rfc8725bis.md

@@ -698,7 +698,7 @@ Also, note that attempting to retrofit mandatory explicit typing
 into the validation rules for existing kinds of JWTs not already using it
 would be a breaking change;
 if a legacy implementation creates a JWT without the explicit type and
-an updated implementation receiving it requres the explicit type,
+an updated implementation receiving it requires the explicit type,
 the JWT will be rejected.  The implementations will not interoperate.
 However, retrofitting a rule that if the JWT contains a "typ" value,
 then it MUST be expected explicit type, is not a breaking change.