diff --git a/IdentityServer/v6/docs/content/fundamentals/resources/api_resources.md b/IdentityServer/v6/docs/content/fundamentals/resources/api_resources.md
index 4571d25f..2ea94d3d 100644
--- a/IdentityServer/v6/docs/content/fundamentals/resources/api_resources.md
+++ b/IdentityServer/v6/docs/content/fundamentals/resources/api_resources.md
@@ -142,7 +142,7 @@ If a client would now request a scope belonging to the *customer* resource, the
 
 ### Setting a signing algorithm
 Your APIs might have certain requirements for the cryptographic algorithm used to sign the access tokens for that resource.
-An example could be regulatory requirements, or that you are starting to migration your system to higher security algorithms.
+An example could be regulatory requirements, or that you are starting to migrate your system to higher security algorithms.
 
 The following sample sets *PS256* as the required signing algorithm for the *invoices* API: