Acrolinx fixes

KarlErickson · KarlErickson · commit 95dac23f8c94 · 2023-07-05T14:25:29.000-07:00
diff --git a/articles/spring-apps/how-to-configure-enterprise-spring-cloud-gateway.md b/articles/spring-apps/how-to-configure-enterprise-spring-cloud-gateway.md
@@ -262,15 +262,15 @@ req.send();
 
 Cross-origin resource sharing (CORS) allows restricted resources on a web page to be requested from another domain outside the domain from which the first resource was served. The available CORS configuration options are described in the following table.
 
-| Property                | Description                                                                       |
-|-------------------------|-----------------------------------------------------------------------------------|
-| `allowedOrigins`        | Allowed origins to make cross-site requests.                                      |
-| `allowedOriginPatterns` | Allowed origin patterns to make cross-site requests.                              |
-| `allowedMethods`        | Allowed HTTP methods on cross-site requests.                                      |
-| `allowedHeaders`        | Allowed headers in cross-site request.                                            |
-| `maxAge`                | How long, in seconds, the response from a preflight request is cached by clients. |
-| `allowCredentials`      | Whether user credentials are supported on cross-site requests.                    |
-| `exposedHeaders`        | HTTP response headers to expose for cross-site requests.                          |
+| Property                | Description                                                                |
+|-------------------------|----------------------------------------------------------------------------|
+| `allowedOrigins`        | Allowed origins to make cross-site requests.                               |
+| `allowedOriginPatterns` | Allowed origin patterns to make cross-site requests.                       |
+| `allowedMethods`        | Allowed HTTP methods on cross-site requests.                               |
+| `allowedHeaders`        | Allowed headers in cross-site request.                                     |
+| `maxAge`                | How long, in seconds, clients cache the response from a preflight request. |
+| `allowCredentials`      | Whether user credentials are supported on cross-site requests.             |
+| `exposedHeaders`        | HTTP response headers to expose for cross-site requests.                   |
 
 > [!NOTE]
 > Be sure you have the correct CORS configuration if you want to integrate with API portal. For more information, see the [Configure Spring Cloud Gateway](#configure-spring-cloud-gateway) section.
@@ -420,7 +420,7 @@ For information on the available metrics, see the [User metrics options](./conce
 
 ## Configure environment variables
 
-Spring Cloud Gateway is managed and tuned by the Azure Spring Apps service. Except for the use cases that configure application performance monitoring and the log level, you don't normally need to configure it with environment variables. But if you do have requirements that you can't fulfill by other configurations described in this article, you can try to configure the environment variables shown in the [Common application properties](https://cloud.spring.io/spring-cloud-gateway/reference/html/appendix.html#common-application-properties) list. Be sure to verify your configuration in your test environment before applying it to your production environment.
+The Azure Spring Apps service manages and tunes Spring Cloud Gateway. Except for the use cases that configure application performance monitoring and the log level, you don't normally need to configure it with environment variables. But if you do have requirements that you can't fulfill by other configurations described in this article, you can try to configure the environment variables shown in the [Common application properties](https://cloud.spring.io/spring-cloud-gateway/reference/html/appendix.html#common-application-properties) list. Be sure to verify your configuration in your test environment before applying it to your production environment.
 
 #### [Azure portal](#tab/Azure-portal)
 
@@ -522,8 +522,8 @@ You can configure the log levels of Spring Cloud Gateway in the following ways t
 - The default log level for Spring Cloud Gateway is `INFO`.
 - You can set log levels to `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `OFF`.
 - You can turn off logs by setting log levels to `OFF`.
-- When log levels are set to `WARN`, `ERROR`, `OFF`, you may be required to adjust it to `INFO` when requesting support from the Azure Spring Apps team. This change will cause a restart of Spring Cloud Gateway.
-- When log levels are set to `TRACE` or `DEBUG`, it may impact the performance of Spring Cloud Gateway. Try avoid these settings in your production environment.
+- When log levels are set to `WARN`, `ERROR`, `OFF`, you may be required to adjust it to `INFO` when requesting support from the Azure Spring Apps team. This change causes a restart of Spring Cloud Gateway.
+- When log levels are set to `TRACE` or `DEBUG`, it may affect the performance of Spring Cloud Gateway. Try avoid these settings in your production environment.
 - You can set log levels for the `root` logger or specific loggers like `io.pivotal.spring.cloud.gateway`.
 
 The following loggers may contain valuable troubleshooting information at the `TRACE` and `DEBUG` levels:
@@ -574,7 +574,7 @@ If the log level is sensitive information in your case, you can include it by us
 
 The addon configuration feature enables you to customize certain properties of Spring Cloud Gateway using a JSON format string. The feature is useful when you need to configure properties that aren't exposed through the REST API.
 
-The addon configuration is a JSON object with key-value paris representing the desired configuration. The following example shows the structure of the JSON format:
+The addon configuration is a JSON object with key-value pairs representing the desired configuration. The following example shows the structure of the JSON format:
 
 ```json
 {
diff --git a/articles/spring-apps/how-to-enterprise-deploy-app-at-scale.md b/articles/spring-apps/how-to-enterprise-deploy-app-at-scale.md
@@ -24,7 +24,7 @@ When you deploy Azure Spring Apps in an Azure virtual network, you need to confi
 
 To avoid this problem, you should reserve subnet ranges that are large enough to support the number of application instances. For subnets, Azure reserves five IP addresses, and Azure Spring Apps requires at least three IP addresses. We recommend that you reserve at least the `/24` subnet ranges for the apps subnet.
 
-For more information about how deploy an Azure Spring Apps instance in your virtual network, see [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
+For more information about how to deploy an Azure Spring Apps instance in your virtual network, see [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
 
 ## Restrictions
 
