diff --git a/README.md b/README.md
index 749d311..65c4651 100644
--- a/README.md
+++ b/README.md
@@ -20,6 +20,8 @@ This repository contains documentation, guides, and reference material.
   Documentation and guides related to Keycloak configuration and best practices.  
   - [Enforce OTP 2FA for Internal Users](./keycloak/enforce-otp-internal.md)  
     Step-by-step instructions for enforcing OTP-based two-factor authentication for internal users, while excluding external Microsoft Entra users.
+  - [Integrate MS Entra in Keycloak as IDP](./keycloak/idp-ms-entra.md)
+    Step-by-step instructions for integrating MS Entra as identity-provider.
 
 - **[Microsoft Entra](./ms-entra/)**  
   Documentation and guides related to Microsft Entra configuration and best practices.
diff --git a/keycloak/idp-ms-entra.md b/keycloak/idp-ms-entra.md
index 703919b..ef26d97 100644
--- a/keycloak/idp-ms-entra.md
+++ b/keycloak/idp-ms-entra.md
@@ -11,7 +11,7 @@ From the [Entra guide](../ms-entra/enterprise-app-keycloak.md) you should have:
 - **Client secret (Value)**
 - (Optional) **Tenant ID** — useful to verify you used the correct discovery URL
 
-You’ll also need:
+You'll also need:
 - Access to the **Keycloak Admin Console**
 - The **realm** where you want to add the provider (e.g., `Digitalboard`)
 - The **alias** you decided on (this must match the alias in the Entra Redirect URI)
@@ -54,7 +54,7 @@ On the **Add identity provider** form:
 ---
 
 ## Step 3 — Set recommended options
-After saving, on the provider’s **Settings** tab, adjust:
+After saving, on the provider's **Settings** tab, adjust:
 
 - **Default Scopes**: `openid profile email`  
   (ensures Entra returns the claims you added in the [Entra guide](../ms-entra/enterprise-app-keycloak.md))
@@ -70,12 +70,12 @@ Click **Save**.
 ## Step 3 — Check the provider appears on the login page
 Back on **Configure → Identity providers**, you should see your new provider listed.
 
-Open your realm’s login page (or log out of the Admin Console and choose **Sign in with <Provider-Display-Name>**). You should be redirected to Microsoft, then back to Keycloak, and end up authenticated.
+Open your realm's login page (or log out of the Admin Console and choose **Sign in with <Provider-Display-Name>**). You should be redirected to Microsoft, then back to Keycloak, and end up authenticated.
 
 ---
 
 ## Troubleshooting
 - **`invalid_redirect_uri` (on Microsoft)**: The Redirect URI in Entra must match exactly what Keycloak shows (including realm name and **alias**).
-- **`AADSTS50105`**: Access to the Enterprise App is restricted. Follow Steps 10–11 in the [Entra guide](../ms-entra/enterprise-app-keycloak.md) to assign the user/group.
+- **`AADSTS50105`**: Access to the Enterprise App is restricted. Follow Steps 10-11 in the [Entra guide](../ms-entra/enterprise-app-keycloak.md) to assign the user/group.
 - **No name/email in Keycloak user**: Check **Default Scopes** include `profile email`, verify Entra **Token configuration** (claims) and Keycloak **Mappers**.
 - **Issuer/metadata errors**: Ensure the **Discovery endpoint** uses your real **tenant ID** and is reachable over HTTPS from Keycloak.