diff --git a/policies/migrate-to-entra-external-id-for-customers/readme.md b/policies/migrate-to-entra-external-id-for-customers/readme.md
index 843a8dda..10d107d0 100644
--- a/policies/migrate-to-entra-external-id-for-customers/readme.md
+++ b/policies/migrate-to-entra-external-id-for-customers/readme.md
@@ -6,7 +6,7 @@ This sample will use AAD B2C as the journey orchestrator, whilst creating and au
 
 ## How it works
 
-Users are sent to the AAD B2C authentiaction endpoint. An Azure function orchestrates all Read/Write operations to the Entra External Id directory.
+Users are sent to the AAD B2C authentication endpoint. An Azure function orchestrates all Read/Write operations to the Entra External Id directory.
 
 ![High level design](media/high-level-design.png)
 
@@ -53,4 +53,4 @@ Scenarios to test:
 1. Assign the user to a group/role in Entra External Id tenant, then perform a sign in
 1. Create a User Flow in Entra External Id tenant, and perform a Sign In via Entra External Id tenant with an account that was created via this AAD B2C custom policy
 1. Sign in via this AAD B2C custom policy with an account that was created using the User Flow from Entra External Id tenant
-1. View the User Profile after Sign Up in the Entra External Id tenant. Ensure the `Authentication Methods` menu is correctly populated with the users phone number visible, after sign up via this AAD B2C custom policy
\ No newline at end of file
+1. View the User Profile after Sign Up in the Entra External Id tenant. Ensure the `Authentication Methods` menu is correctly populated with the users phone number visible, after sign up via this AAD B2C custom policy