diff --git a/IdentityServer/v7/docs/content/ui/custom.md b/IdentityServer/v7/docs/content/ui/custom.md
index bc77defb..787ba408 100644
--- a/IdentityServer/v7/docs/content/ui/custom.md
+++ b/IdentityServer/v7/docs/content/ui/custom.md
@@ -16,7 +16,7 @@ Duende IdentityServer provides the [authorize interaction response generator]({{
 
 ### Built-in AuthorizeInteractionResponseGenerator
 
-To provide custom logic for the authorize endpoint, the recommondation is to derive from the built-in *AuthorizeInteractionResponseGenerator* to inherit all the default logic pertaining to login and consent semantics.
+To provide custom logic for the authorize endpoint, the recommendation is to derive from the built-in *AuthorizeInteractionResponseGenerator* to inherit all the default logic pertaining to login and consent semantics.
 To augment the built-in logic, override *ProcessLoginAsync* and/or *ProcessConsentAsync* (depending on the nature of the custom logic).
 The pattern would be to invoke the base implementation and if the result did not cause a login, consent or error, then the custom logic could be tested to determine if it is desired to prevent SSO and instead force the user to interact in some way (e.g. re-login, trigger MFA, accept a EULA, etc).
 The sample below illustrates: