diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/external-authentication.md b/deploy-manage/users-roles/cluster-or-deployment-auth/external-authentication.md
index 4962efa7b5..6da2a91478 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/external-authentication.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/external-authentication.md
@@ -13,7 +13,7 @@ External authentication in Elastic is any form of authentication that requires i
 
 Elastic offers several external [realm](authentication-realms.md) types, each of which represents a common authentication provider. You can have as many external realms as you would like, each with its own unique name and configuration.
 
-If the authentication provider that you want to use is not currently supported, then you can create a your own [custom realm plugin](custom.md) to integrate with additional systems.
+If the authentication provider that you want to use is not currently supported, then you can create your own [custom realm plugin](custom.md) to integrate with additional systems.
 
 In this section, you'll learn how to configure different types of external realms, and use them to grant access to Elastic resources.
 
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md b/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md
index 44f945810c..b6a4ebcf6a 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md
@@ -284,7 +284,7 @@ You can relax validation of any of the time-based claims by setting `allowed_clo
 
 ## Role mapping [jwt-authorization]
 
-You can map LDAP groups to roles in the following ways:
+You can map JWT groups to roles in the following ways:
 
 * Using the role mappings page in {{kib}}.
 * Using the [role mapping API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-put-role-mapping).
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/ldap.md b/deploy-manage/users-roles/cluster-or-deployment-auth/ldap.md
index 616e66b391..cf747f2748 100644
--- a/deploy-manage/users-roles/cluster-or-deployment-auth/ldap.md
+++ b/deploy-manage/users-roles/cluster-or-deployment-auth/ldap.md
@@ -38,7 +38,7 @@ The path to an entry is a *Distinguished Name* (DN) that uniquely identifies a u
 The `ldap` realm supports two modes of operation, a user search mode and a mode with specific templates for user DNs.
 
 ::::{important}
-When you configure realms in `elasticsearch.yml`/deploy-manage/stack-settings.md, only the realms you specify are used for authentication. If you also want to use the `native` or `file` realms, you must include them in the realm chain.
+When you configure realms in [`elasticsearch.yml`](/deploy-manage/stack-settings.md), only the realms you specify are used for authentication. If you also want to use the `native` or `file` realms, you must include them in the realm chain.
 ::::
 
 ## Step 1: Add a new realm configuration [ldap-realm-configuration]