From dbc1d3abf668747513bc070fffb20882cc655152 Mon Sep 17 00:00:00 2001
From: GitHubPang <61439577+GitHubPang@users.noreply.github.com>
Date: Wed, 6 Jul 2022 13:40:15 +0800
Subject: [PATCH] Fix misspelling. (#26329)

---
 aspnetcore/security/authorization/claims.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/aspnetcore/security/authorization/claims.md b/aspnetcore/security/authorization/claims.md
index f3d093e675..e9be613e7b 100644
--- a/aspnetcore/security/authorization/claims.md
+++ b/aspnetcore/security/authorization/claims.md
@@ -56,7 +56,7 @@ If you have a controller that's protected by the `[Authorize]` attribute, but wa
 
 [!code-csharp[](~/security/authorization/claims/samples/6.x/WebAll/Controllers/VacationController.cs?name=snippet&highlight=14)]
 
-Because policies can ***not*** be applied at the Razor Page handler level, we recommend using a controller when polices must be applied at the page handler level. The rest of the app that doesn't require policies at the Razor Page handler level can use Razor Pages.
+Because policies can ***not*** be applied at the Razor Page handler level, we recommend using a controller when policies must be applied at the page handler level. The rest of the app that doesn't require policies at the Razor Page handler level can use Razor Pages.
 
 Most claims come with a value. You can specify a list of allowed values when creating the policy. The following example would only succeed for employees whose employee number was 1, 2, 3, 4 or 5.