Fixing rendering issues and links.

docs/en/operations/external-authenticators/index.md

@@ -10,4 +10,4 @@ ClickHouse supports authenticating and managing users using external services.
 
 The following external authenticators and directories are supported:
 
-- [LDAP](#external-authenticators-ldap) [Authenticator](#ldap-external-authenticator) and [Directory](#ldap-external-user-directory)
+- [LDAP](./ldap.md#external-authenticators-ldap) [Authenticator](./ldap.md#ldap-external-authenticator) and [Directory](./ldap.md#ldap-external-user-directory)

docs/en/operations/external-authenticators/ldap.md

@@ -5,8 +5,7 @@ LDAP server can be used to authenticate ClickHouse users. There are two differen
 - use LDAP as an external authenticator for existing users, which are defined in `users.xml` or in local access control paths
 - use LDAP as an external user directory and allow locally undefined users to be authenticated if they exist on the LDAP server
 
-For both of these approaches, an internally named LDAP server must be defined in the ClickHouse config 
-so that other parts of config are able to refer to it.
+For both of these approaches, an internally named LDAP server must be defined in the ClickHouse config so that other parts of config are able to refer to it.
 
 ## LDAP Server Definition {#ldap-server-definition}
 
@@ -34,7 +33,7 @@ To define LDAP server you must add `ldap_servers` section to the `config.xml`. F
 </yandex>
 ```
 
-Note, that you can define multiple LDAP servers inside `ldap_servers` section using distinct names.
+Note, that you can define multiple LDAP servers inside the `ldap_servers` section using distinct names.
 
 Parameters:
 
@@ -65,8 +64,7 @@ Parameters:
 
 A remote LDAP server can be used as a method for verifying passwords for locally defined users (users defined in `users.xml` or in local access control paths). In order to achieve this, specify previously defined LDAP server name instead of `password` or similar sections in the user definition.
 
-At each login attempt, ClickHouse will try to "bind" to the specified DN defined by the `bind_dn` parameter
-in the [LDAP server definition](#ldap-server-definition) using the provided credentials, and if successful, the user will be considered authenticated. This is often called a "simple bind" method.
+At each login attempt, ClickHouse will try to "bind" to the specified DN defined by the `bind_dn` parameter in the [LDAP server definition](#ldap-server-definition) using the provided credentials, and if successful, the user will be considered authenticated. This is often called a "simple bind" method.
 
 For example,
 
@@ -87,7 +85,7 @@ For example,
 
 Note, that user `my_user` refers to `my_ldap_server`. This LDAP server must be configured in the main `config.xml` file as described previously.
 
-When SQL-driven [Access Control and Account Management](#access-control) is enabled in ClickHouse, users that are identified by LDAP servers can also be created using the [CRATE USER](#create-user-statement) statement.
+When SQL-driven [Access Control and Account Management](../access-rights.md#access-control) is enabled in ClickHouse, users that are authenticated by LDAP servers can also be created using the [CRATE USER](../../sql-reference/statements/create/user.md#create-user-statement) statement.
 
 
 ```sql
@@ -96,9 +94,9 @@ CREATE USER my_user IDENTIFIED WITH ldap_server BY 'my_ldap_server'
 
 ## LDAP Exernal User Directory {#ldap-external-user-directory}
 
-In addition to the locally defined users, a remote LDAP server can be used as a source of user definitions. In order to achieve this, specify previously defined LDAP server name (see [LDAP Server Definition](#ldap-server-definition)) in the `ldap` section inside the `users_directories` section in of the `config.xml` file.
+In addition to the locally defined users, a remote LDAP server can be used as a source of user definitions. In order to achieve this, specify previously defined LDAP server name (see [LDAP Server Definition](#ldap-server-definition)) in the `ldap` section inside the `users_directories` section of the `config.xml` file.
 
-At each login attempt, ClickHouse will try to find the user definition locally and authenticate it as usual, but if the user is not defined, ClickHouse will assume it exists in the external LDAP directory, and will try to "bind" to the specified DN at the LDAP server using the provided credentials, and if successful, the user will be considered existing and authenticated. The user will be assigned roles from the list specified in the `roles` section. Additionally, LDAP "search" can be performed and results can be transformed and treated as role names and then assigned to the user if the `role_mapping` section is also configured. All this implies that the SQL-driven [Access Control and Account Management](#access-control) is enabled in ClickHouse and roles are created using the [CREATE ROLE](#create-role-statement) statement.
+At each login attempt, ClickHouse will try to find the user definition locally and authenticate it as usual, but if the user is not defined, ClickHouse will assume it exists in the external LDAP directory, and will try to "bind" to the specified DN at the LDAP server using the provided credentials. If successful, the user will be considered existing and authenticated. The user will be assigned roles from the list specified in the `roles` section. Additionally, LDAP "search" can be performed and results can be transformed and treated as role names and then be assigned to the user if the `role_mapping` section is also configured. All this implies that the SQL-driven [Access Control and Account Management](../access-rights.md#access-control) is enabled and roles are created using the [CREATE ROLE](../../sql-reference/statements/create/role.md#create-role-statement) statement.
 
 Example (goes into `config.xml`):
 
@@ -130,7 +128,7 @@ defined LDAP server that is configured in the `config.xml` (see [LDAP Server Def
 
 Parameters:
 
-- `server` - one of LDAP server names defined in `ldap_servers` config section above.
+- `server` - one of LDAP server names defined in the `ldap_servers` config section above.
   This parameter is mandatory and cannot be empty.
 - `roles` - section with a list of locally defined roles that will be assigned to each user retrieved from the LDAP server.
     - If no roles are specified here or assigned during role mapping (below), user will not be able
@@ -140,7 +138,7 @@ Parameters:
       and the name of the logged in user. For each entry found during that search, the value of the specified
       attribute is extracted. For each attribute value that has the specified prefix, the prefix is removed,
       and the rest of the value becomes the name of a local role defined in ClickHouse,
-    which is expected to be created beforehand by the [CREATE ROLE](#create-role-statement) statement.
+      which is expected to be created beforehand by the [CREATE ROLE](../../sql-reference/statements/create/role.md#create-role-statement) statement.
     - There can be multiple `role_mapping` sections defined inside the same `ldap` section. All of them will be applied.
         - `base_dn` - template used to construct the base DN for the LDAP search.
            - The resulting DN will be constructed by replacing all `{user_name}` and `{bind_dn}`