edits

Author: KarlErickson

articles/spring-apps/basic-standard/how-to-appdynamics-java-agent-monitor.md

@@ -220,7 +220,7 @@ You can define more metrics for the JVM, as shown in this screenshot of the **Me
 
 ## View AppDynamics Agent logs
 
-By default, Azure Spring Apps will print the *info* level logs of the AppDynamics Agent to `STDOUT`. The logs will be mixed with the application logs. You can find the explicit agent version from the application logs.
+By default, Azure Spring Apps prints the *info* level logs of the AppDynamics Agent to `STDOUT`. The logs are mixed with the application logs. You can find the explicit agent version from the application logs.
 
 You can also get the logs of the AppDynamics Agent from the following locations:
 
@@ -230,10 +230,10 @@ You can also get the logs of the AppDynamics Agent from the following locations:
 
 ## Learn about AppDynamics Agent upgrade
 
-The AppDynamics Agent will be upgraded regularly with JDK (quarterly). Agent upgrade may affect the following scenarios:
+The AppDynamics Agent is upgraded regularly with JDK (quarterly). Agent upgrade might affect the following scenarios:
 
-* Existing applications using AppDynamics Agent before upgrade will be unchanged, but will require restart or redeploy to engage the new version of AppDynamics Agent.
-* Applications created after upgrade will use the new version of AppDynamics Agent.
+- Existing applications using AppDynamics Agent before upgrade are unchanged, but require restart or redeploy to engage the new version of AppDynamics Agent.
+- Applications created after upgrade use the new version of AppDynamics Agent.
 
 ## Configure virtual network injection instance outbound traffic
 

articles/spring-apps/enterprise/concept-app-status.md

@@ -50,16 +50,14 @@ The provisioning state is accessible only from the CLI. The status is reported a
 | Value     | Definition                                              |
 |-----------|---------------------------------------------------------|
 | Creating  | The resource is creating and isn't ready.              |
-| Updating  | The resource is updating and the functionality may be different from the deployment definition until the update is complete.                               |
+| Updating  | The resource is updating and the functionality might be different from the deployment definition until the update is complete.                               |
 | Succeeded | Successfully supplied resources and deploys the binary. The deployment's functionality is the same as the definition and all app instances are working. |
 | Failed    | Failed to achieve the *Succeeded* goal.                 |
 | Deleting  | The resource is being deleted which prevents operation, and the resource isn't available in this status. |
 
 ### Registration status
 
-The app registration status shows the state in service discovery. Azure Spring Apps in Basic/Standard plan uses Eureka for service discovery. For more information on how the Eureka client calculates the state, see [Eureka's health checks](https://cloud.spring.io/spring-cloud-static/Greenwich.RELEASE/multi/multi__service_discovery_eureka_clients.html#_eureka_s_health_checks).
-
-The Enterprise pricing plan uses [Tanzu Service Registry](how-to-enterprise-service-registry.md) for service discovery.
+The app registration status shows the state in service discovery. The Basic/Standard plan uses Eureka for service discovery. For more information on how the Eureka client calculates the state, see [Eureka's health checks](https://cloud.spring.io/spring-cloud-static/Greenwich.RELEASE/multi/multi__service_discovery_eureka_clients.html#_eureka_s_health_checks). The Enterprise pricing plan uses [Tanzu Service Registry](how-to-enterprise-service-registry.md) for service discovery.
 
 ## App instances status
 
@@ -76,10 +74,10 @@ The instance status is reported as one of the following values:
 
 | Value       | Definition |
 |-------------|------------|
-| Starting    | The binary is successfully deployed to the given instance. The instance booting the jar file may fail because the jar can't run properly. Azure Spring Apps will restart the app instance in 60 seconds if it detects that the app instance is still in the *Starting* state. |
+| Starting    | The binary is successfully deployed to the given instance. The instance booting the jar file might fail because the jar can't run properly. Azure Spring Apps restarts the app instance in 60 seconds if it detects that the app instance is still in the *Starting* state. |
 | Running     | The instance works. The instance can serve requests from inside Azure Spring Apps. |
-| Failed      | The app instance failed to start the user's binary after several retries. The app instance may be in one of the following states:<br/>- The app may stay in the *Starting* status and never be ready for serving requests.<br/>- The app may boot up but crashed in a few seconds. |
-| Terminating | The app instance is shutting down. The app may not serve requests and the app instance will be removed. |
+| Failed      | The app instance failed to start the user's binary after several retries. The app instance might be in one of the following states:<br/>- The app might stay in the *Starting* status and never be ready for serving requests.<br/>- The app might boot up but crashed in a few seconds. |
+| Terminating | The app instance is shutting down. The app might not serve requests and the app instance is removed. |
 
 ### App discovery status
 

articles/spring-apps/enterprise/concept-manage-monitor-app-spring-boot-actuator.md

@@ -18,19 +18,21 @@ ms.custom: devx-track-java
 
 **This article applies to:** ✔️ Basic/Standard ✔️ Enterprise
 
-Spring Boot Actuator brings production-ready features to your apps. You can effortlessly monitor your app, collect metrics, and understand the status or database activity with this tool. Most importantly, you can gain access to professional-grade tools without needing to build them from scratch.
+Spring Boot Actuator brings production-ready features to your apps. You can effortlessly monitor your app, collect metrics, and understand the status or database activity with this tool. You gain access to professional-grade tools without needing to build them from scratch.
 
-The actuator exposes vital operational data about your running application, like health status, metrics, information, and more by using the HTTP endpoints or Java Management Extensions (JMX), making it easy to interact with. Once integrated, it provides several default endpoints, and like other Spring modules, it's easily configurable and extendable.
+The actuator exposes vital operational data about your running application, like health status, metrics, information, and more. The actuator uses HTTP endpoints or Java Management Extensions (JMX), making it easy to interact with. After you integrate it, it provides several default endpoints, and like other Spring modules, it's easily configurable and extendable.
 
-In Azure Spring Apps service instance, actuator is used for enriching metrics by using JMX. It can also work with Application Live View in Enterprise plan to help you get and interact with the data from apps.
+Azure Spring Apps uses the actuator for enriching metrics through JMX. It can also work with Application Live View in the Enterprise plan to help you get and interact with the data from apps.
 
 :::image type="content" source="media/concept-manage-monitor-app-spring-boot-actuator/data-flow.png" alt-text="Diagram that shows the data flow using Spring Boot Actuator." lightbox="media/concept-manage-monitor-app-spring-boot-actuator/data-flow.png":::
 
 ## Configure Spring Boot Actuator
 
+The following sections describe how to configure the actuator.
+
 ### Add actuator dependency
 
-To add the actuator to a Maven-based project, add the `Starter` dependency:
+To add the actuator to a Maven-based project, add the following dependency:
 
 ```xml
 <dependencies>
@@ -41,13 +43,11 @@ To add the actuator to a Maven-based project, add the `Starter` dependency:
 </dependencies>
 ```
 
-This configuration holds true for any Spring Boot version as versions are outlined in the Spring Boot Bill of Materials (BOM).
+This configuration works any Spring Boot version because versions are covered in the Spring Boot Bill of Materials (BOM).
 
 ### Configure actuator endpoint
 
-By default, Spring Boot application exposes the `health` endpoint only.
-
-To observe the configuration and configurable environment, you need to enable `env` and `configprops` endpoints as well.
+By default, a Spring Boot application exposes the `health` endpoint only. To observe the configuration and configurable environment, use the following steps to enable the `env` and `configprops` endpoints as well:
 
 1. Go to app **Overview** pane, select **Configuration** in the setting menu, and then go to the **Environment variables** configuration page.
 1. Add the following properties as in the "key:value" form. This environment opens the following Spring Actuator endpoints: `health`, `env`, and `configprops`.
@@ -64,9 +64,9 @@ To view all the endpoints built-in and related configurations, see the [Exposing
 
 ## Secure actuator endpoint
 
-When you open the app to public, these actuator endpoints are exposed to public as well. To hide all endpoints, set `management.endpoints.web.exposure.exclude=*`, because `exclude` property takes precedence over the `include` property. This action might block Application Live View in Enterprise plan, or other apps or tools relying on the actuator HTTP endpoint.
+When you open the app to the public, these actuator endpoints are exposed to the public as well. We recommend that you hide all endpoints by setting `management.endpoints.web.exposure.exclude=*`, because the `exclude` property takes precedence over the `include` property. Be aware that this action blocks Application Live View in the Enterprise plan and other apps or tools that rely on the actuator HTTP endpoint.
 
-In the Enterprise plan, you can disable public endpoint of apps and configure VMware Spring Cloud Gateway to disable actuator access from public. For more information, see [Configure VMware Spring Cloud Gateway](./how-to-configure-enterprise-spring-cloud-gateway.md) 
+In the Enterprise plan, you can disable the public endpoint of apps and configure a routing rule in VMware Spring Cloud Gateway to disable actuator access from the public. For more information, see [Configure VMware Spring Cloud Gateway](./how-to-configure-enterprise-spring-cloud-gateway.md).
 
 ## Next steps
 

articles/spring-apps/enterprise/how-to-start-stop-delete.md

@@ -28,9 +28,9 @@ This guide explains how to change an application's state in Azure Spring Apps by
 
 ## Application state
 
-Your applications running in Azure Spring Apps may not need to run continuously. For example, an application may not always need to run if it's used only during business hours.
+Your applications running in Azure Spring Apps might not need to run continuously. For example, an application might not always need to run if it's used only during business hours.
 
-There may be times where you wish to stop or start an application. You can also restart an application as part of general troubleshooting steps or delete an application you no longer require.
+There might be times where you wish to stop or start an application. You can also restart an application as part of general troubleshooting steps or delete an application you no longer require.
 
 ## Manage application state
 

articles/spring-apps/enterprise/troubleshoot.md

@@ -22,7 +22,7 @@ This article provides instructions for troubleshooting Azure Spring Apps develop
 
 ### My application can't start
 
-When your application can't start, you may find that its endpoint can't be connected or it returns a 502 after a few retries.
+When your application can't start, you might find that its endpoint can't be connected or it returns a 502 after a few retries.
 
 For troubleshooting, export the logs to Azure Log Analytics. The table for Spring application logs is named *AppPlatformLogsforSpring*. To learn more, see [Analyze logs and metrics with diagnostics settings](diagnostic-services.md).
 
@@ -270,7 +270,7 @@ Creating an Azure Spring Apps Enterprise plan instance fails with error code "11
 
 ### No plans are available for market '\<Location>'
 
-When you visit the SaaS offer [Azure Spring Apps Enterprise](https://aka.ms/ascmpoffer) in the Azure Marketplace, it may say "No plans are available for market '\<Location>'" as in the following image.
+When you visit the SaaS offer [Azure Spring Apps Enterprise](https://aka.ms/ascmpoffer) in the Azure Marketplace, it might say "No plans are available for market '\<Location>'" as in the following image.
 
 :::image type="content" source="./media/troubleshoot/no-enterprise-plans-available.png" alt-text="Screenshot of the Azure portal that shows the No plans are available for market error message." lightbox="./media/troubleshoot/no-enterprise-plans-available.png":::