diff --git a/docs/extend/extend-apiml/api-mediation-oidc-authentication.md b/docs/extend/extend-apiml/api-mediation-oidc-authentication.md
index d39dd7898b..1ce90439e7 100644
--- a/docs/extend/extend-apiml/api-mediation-oidc-authentication.md
+++ b/docs/extend/extend-apiml/api-mediation-oidc-authentication.md
@@ -154,7 +154,7 @@ User specified parameters are presented in the section [Parameters in the ESM co
 - **distributed-identity-user-name**  
    Specifies the user ID for distributed-identity-registry.
 - **distributed-identity-registry-name**  
-   Specifies the registry value for under which the user is defined in the ESM.
+   Specifies the registry value under which the user is defined in the ESM.
 - **label-name**  
    Specifies the name for the distributed-identity mapping filter.
 
diff --git a/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md b/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md
index e81c5fd99f..917f408d0f 100644
--- a/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md
+++ b/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md
@@ -50,7 +50,7 @@ The Central API ML can onboard Gateways of all domains. This service onboarding
 
 #### Dynamic configuration: YML
 
-Users must set the following property for the Domain Gateway to dynamically onboard to the Central Discovery service.
+Set the following property for the Domain Gateway to dynamically onboard to the Central Discovery service.
 
 `components.gateway.apiml.service.additionalRegistration`
 
@@ -63,17 +63,17 @@ components.gateway.apiml.service.additionalRegistration:
        - discoveryServiceUrls: https://sys1:{discoveryServicePort}/eureka/,https://sys2:{discoveryServicePort}/eureka/
 ```
 
-:::note
-  Ensure that each API ML instance is defined in a separated record. Do not combine multiple API ML instances in a
-  single record. In the case of a high availability setup, the value `discoveryServiceUrls` may contain multiple URLs.
-  We highly recommend to provide all available Discovery URLs in the value `discoveryServiceUrls`.
+:::note Notes:
+* Ensure that each API ML instance is defined in a separated record. Do not combine multiple API ML instances in a single record. In the case of a high availability setup, the value `discoveryServiceUrls` may contain multiple URLs.
+
+* We highly recommend to provide all available Discovery URLs in the value `discoveryServiceUrls`.
 
-  Always provide the direct address to the system. Do not use the DVIPA address. Using this address could lead to unexpected behaviour.
+* Always provide the direct address to the system. Do not use the DVIPA address. Using this address could lead to unexpected behaviour.
 
-  Use hostnames `sys1` and `sys2` for the LPAR in the sysplex.
+* Use hostnames `sys1` and `sys2` for the LPAR in the sysplex.
 :::
 
-The Gateway service can be configured to forward client certificates. The domain gateway can then use this client certificate for authentication. To make sure that only the Gateway-forwarded certificate are used for client certificate authentication, users must set `certificatesUrl` property. This URL returns certificate chain from the central gateway.
+The Gateway service can be configured to forward client certificates. The domain gateway can then use this client certificate for authentication. To make sure that only  Gateway-forwarded certificates are used for client certificate authentication, users must set the `certificatesUrl` property. This URL returns a certificate chain from the central gateway.
 
 ```
 components.gateway.apiml.security.x509: