From 7166e1a1c07027c7a968e04af68905884d486914 Mon Sep 17 00:00:00 2001 From: 1000TurquoisePogs Date: Wed, 6 Nov 2024 19:03:14 +0100 Subject: [PATCH] Grammar and style fixes for all versions Signed-off-by: 1000TurquoisePogs --- ...ration-unique-cookie-name-for-multiple-zowe-instances.md | 6 +++--- ...ration-unique-cookie-name-for-multiple-zowe-instances.md | 6 +++--- ...ration-unique-cookie-name-for-multiple-zowe-instances.md | 6 +++--- ...ration-unique-cookie-name-for-multiple-zowe-instances.md | 6 +++--- ...ration-unique-cookie-name-for-multiple-zowe-instances.md | 6 +++--- 5 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md b/docs/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md index d234bbab31..681a65a3d6 100644 --- a/docs/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md +++ b/docs/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md @@ -9,13 +9,13 @@ To prevent overwriting of the default cookie name in the case of multiple Zowe i Follow this procedure to configure a unique cookie name for the instances: 1. Open the Zowe YAML configuration file. -2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. +2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. 3. Find the property `zowe.cookieIdentifier` and set it to any word or number that you wish to identify your Zowe instance. 4. Restart Zowe. -This will set a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. +This sets a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. **Example:** - If `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name will be `apimlAuthenticationToken.1`. + If the `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name is `apimlAuthenticationToken.1`. If this property is not set to `true`, the cookie name remains the default value `apimlAuthenticationToken`. diff --git a/versioned_docs/version-v2.15.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md b/versioned_docs/version-v2.15.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md index d234bbab31..681a65a3d6 100644 --- a/versioned_docs/version-v2.15.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md +++ b/versioned_docs/version-v2.15.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md @@ -9,13 +9,13 @@ To prevent overwriting of the default cookie name in the case of multiple Zowe i Follow this procedure to configure a unique cookie name for the instances: 1. Open the Zowe YAML configuration file. -2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. +2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. 3. Find the property `zowe.cookieIdentifier` and set it to any word or number that you wish to identify your Zowe instance. 4. Restart Zowe. -This will set a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. +This sets a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. **Example:** - If `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name will be `apimlAuthenticationToken.1`. + If the `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name is `apimlAuthenticationToken.1`. If this property is not set to `true`, the cookie name remains the default value `apimlAuthenticationToken`. diff --git a/versioned_docs/version-v2.16.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md b/versioned_docs/version-v2.16.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md index d234bbab31..681a65a3d6 100644 --- a/versioned_docs/version-v2.16.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md +++ b/versioned_docs/version-v2.16.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md @@ -9,13 +9,13 @@ To prevent overwriting of the default cookie name in the case of multiple Zowe i Follow this procedure to configure a unique cookie name for the instances: 1. Open the Zowe YAML configuration file. -2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. +2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. 3. Find the property `zowe.cookieIdentifier` and set it to any word or number that you wish to identify your Zowe instance. 4. Restart Zowe. -This will set a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. +This sets a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. **Example:** - If `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name will be `apimlAuthenticationToken.1`. + If the `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name is `apimlAuthenticationToken.1`. If this property is not set to `true`, the cookie name remains the default value `apimlAuthenticationToken`. diff --git a/versioned_docs/version-v2.17.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md b/versioned_docs/version-v2.17.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md index d234bbab31..681a65a3d6 100644 --- a/versioned_docs/version-v2.17.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md +++ b/versioned_docs/version-v2.17.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md @@ -9,13 +9,13 @@ To prevent overwriting of the default cookie name in the case of multiple Zowe i Follow this procedure to configure a unique cookie name for the instances: 1. Open the Zowe YAML configuration file. -2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. +2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. 3. Find the property `zowe.cookieIdentifier` and set it to any word or number that you wish to identify your Zowe instance. 4. Restart Zowe. -This will set a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. +This sets a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. **Example:** - If `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name will be `apimlAuthenticationToken.1`. + If the `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name is `apimlAuthenticationToken.1`. If this property is not set to `true`, the cookie name remains the default value `apimlAuthenticationToken`. diff --git a/versioned_docs/version-v2.18.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md b/versioned_docs/version-v2.18.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md index d234bbab31..681a65a3d6 100644 --- a/versioned_docs/version-v2.18.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md +++ b/versioned_docs/version-v2.18.x/user-guide/api-mediation/configuration-unique-cookie-name-for-multiple-zowe-instances.md @@ -9,13 +9,13 @@ To prevent overwriting of the default cookie name in the case of multiple Zowe i Follow this procedure to configure a unique cookie name for the instances: 1. Open the Zowe YAML configuration file. -2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. +2. Find or add the property `components.gateway.apiml.security.auth.uniqueCookie`, and set it to `true`. 3. Find the property `zowe.cookieIdentifier` and set it to any word or number that you wish to identify your Zowe instance. 4. Restart Zowe. -This will set a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. +This sets a suffix for the API Gateway's cookie name based upon the value of `zowe.cookieIdentifier`. **Example:** - If `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name will be `apimlAuthenticationToken.1`. + If the `components.gateway.apiml.security.auth.uniqueCookie` parameter is set to `true` and `zowe.cookieIdentifier` is `1`, the cookie name is `apimlAuthenticationToken.1`. If this property is not set to `true`, the cookie name remains the default value `apimlAuthenticationToken`.