Merge branch 'reboot/additional-ds-registration-fix' of https://githu…

…b.com/zowe/docs-site into reboot/additional-ds-registration-fix
zowe · Oct 17, 2024 · 29c7d23 · 29c7d23
2 parents b7784cd + 37ea6d9
commit 29c7d23
Show file tree

Hide file tree

Showing 2 changed files with 19 additions and 14 deletions.
diff --git a/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md b/docs/user-guide/api-mediation/api-mediation-multi-tenancy.md
@@ -73,8 +73,10 @@ components.gateway.apiml.service.additionalRegistration:
                 serviceUrl: /
 ```
 
-:::note 
-  Ensure that each API ML instance is defined in a separate 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
+  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.
 
@@ -133,8 +135,10 @@ components.gateway.apiml.service.additionalRegistration:
                 serviceUrl: /
 ```
 
-:::note 
-  Ensure that each API ML instance is defined in a separate 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
+  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.
 
@@ -157,13 +161,13 @@ ZWE_CONFIGS_APIML_SERVICE_ADDITIONALREGISTRATION_0_ROUTES_0_SERVICEURL=/
   The number in the properties names (see position of `#` in `ZWE_CONFIGS_APIML_SERVICE_ADDITIONALREGISTRATION_#_*`)
   defines ID of API ML instance.
 
-  Each API ML instance should be defined in a separated record. Do not mix different API ML instance in one record.
-  The value `discoveryServiceUrls` could contain multiple URLs in case of HA setup. We highly recommend to provide all
-  available Discovery URLs in there.
+  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 DVIPA address. It 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.
 
-  Hostnames `sys1` and `sys2` are names of LPAR in the sysplex.
+  Use hostnames `sys1` and `sys2` for the LPAR in the sysplex.
 :::
 
 This Zowe configuration transforms the zowe.yaml configuration file into the environment variables described previously. 

diff --git a/docs/user-guide/api-mediation/configuration-multi-tenancy-routing.md b/docs/user-guide/api-mediation/configuration-multi-tenancy-routing.md
@@ -28,11 +28,12 @@ Follow these steps to register with additional Discovery Services:
                 serviceUrl: /
     ```
 
-  :::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
+     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.
+   :::
 
 3. Restart Zowe.