acrolinx items

Author: mrm9084

articles/azure-app-configuration/enable-dynamic-configuration-java-spring-app.md

@@ -23,7 +23,7 @@ Both libraries support manual triggering to check for refreshed configuration va
 
 Refresh allows you to update your configuration values without having to restart your application, though it causes all beans in the `@RefreshScope` to be recreated. It checks for any changes to configured triggers, including metadata. By default, the minimum amount of time between checks for changes, refresh interval, is set to 30 seconds.
 
-`spring-cloud-azure-appconfiguration-config-web`'s automated refresh is triggered based on activity, specifically Spring Web's `ServletRequestHandledEvent`. If a `ServletRequestHandledEvent` isn't triggered, `spring-cloud-azure-appconfiguration-config-web`'s automated refresh doesn't trigger a refresh even if the cache expiration time has expired.
+`spring-cloud-azure-appconfiguration-config-web`'s automated refresh is triggered based on activity, specifically Spring Web's `ServletRequestHandledEvent`. If a `ServletRequestHandledEvent` isn't triggered, `spring-cloud-azure-appconfiguration-config-web`'s automated refresh doesn't trigger a refresh even if the cache expiration time is expired.
 
 ## Use manual refresh
 
@@ -57,9 +57,9 @@ App Configuration exposes `AppConfigurationRefresh`, which can be used to check
     }
     ```
 
-    `AppConfigurationRefresh`'s `refreshConfigurations()` returns a `Mono` that is true if a refresh has been triggered, and false if not. False means either the cache expiration time hasn't expired, there was no change, or another thread is currently checking for a refresh.
+    `AppConfigurationRefresh`'s `refreshConfigurations()` returns a `Mono` that is true if a refresh is triggered, and false if not. False means either the cache expiration time isn't expired, there was no change, or another thread is currently checking for a refresh.
 
-1.  Update `bootstrap.properties` to enable refresh:
+1.  To enable refresh update `bootstrap.properties`:
 
     ```properties
     spring.cloud.azure.appconfiguration.stores[0].monitoring.enabled=true
@@ -84,7 +84,7 @@ App Configuration exposes `AppConfigurationRefresh`, which can be used to check
     mvn spring-boot:run
     ```
 
-1. Open a browser window, and go to the URL: `http://localhost:8080`.  You see the message associated with your key.
+1. Open a browser window, and go to the URL: `http://localhost:8080`. You see the message associated with your key.
 
     You can also use *curl* to test your application, for example:
 
@@ -98,7 +98,7 @@ App Configuration exposes `AppConfigurationRefresh`, which can be used to check
     |---|---|
     | /application/config.message | Hello - Updated |
 
-1. Update the sentinel key you created earlier to a new value. This change triggers the application to refresh all configuration keys once the refresh interval has passed.
+1. Update the sentinel key you created earlier to a new value. This change triggers the application to refresh all configuration keys once the refresh interval is passed.
 
     | Key | Value |
     |---|---|
@@ -123,7 +123,7 @@ Then, open the *pom.xml* file in a text editor and add a `<dependency>` for `spr
 </dependency>
 ```
 
-1. Update `bootstrap.properties` to enable refresh
+1. To enable refresh update `bootstrap.properties`:
 
     ```properties
     spring.cloud.azure.appconfiguration.stores[0].monitoring.enabled=true
@@ -148,7 +148,7 @@ Then, open the *pom.xml* file in a text editor and add a `<dependency>` for `spr
     mvn spring-boot:run
     ```
 
-1. Open a browser window, and go to the URL: `http://localhost:8080`.  You now see the message associated with your key.
+1. Open a browser window, and go to the URL: `http://localhost:8080`. You now see the message associated with your key.
 
     You can also use *curl* to test your application, for example:
 
@@ -162,7 +162,7 @@ Then, open the *pom.xml* file in a text editor and add a `<dependency>` for `spr
     |---|---|
     | /application/config.message | Hello - Updated |
 
-1. Update the sentinel key you created earlier to a new value. This change triggers the application to refresh all configuration keys once the refresh interval has passed.
+1. Update the sentinel key you created earlier to a new value. This change triggers the application to refresh all configuration keys once the refresh interval is passed.
 
     | Key | Value |
     |---|---|

articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md

@@ -17,7 +17,7 @@ ms.author: mametcal
 
 The App Configuration Java Spring client library supports updating configuration on demand without causing an application to restart. An application can be configured to detect changes in App Configuration using one or both of the following two approaches.
 
-- Poll Model: This is the default behavior that uses polling to detect changes in configuration. Once the cached value of a setting expires, the next call to `AppConfigurationRefresh`'s `refreshConfigurations` sends a request to the server to check if the configuration has changed, and pulls the updated configuration if needed.
+- Poll Model: The Poll Model is the default behavior that uses polling to detect changes in configuration. Once the cached value of a setting expires, the next call to `AppConfigurationRefresh`'s `refreshConfigurations` sends a request to the server to check if the configuration changed, and pulls the updated configuration if needed.
 
 - Push Model: This uses [App Configuration events](./concept-app-configuration-event.md) to detect changes in configuration. Once App Configuration is set up to send key value change events with Event Grid, with a [Web Hook](../event-grid/handler-event-hubs.md), the application can use these events to optimize the total number of requests needed to keep the configuration updated.
 
@@ -77,7 +77,7 @@ In this tutorial, you learn how to:
    mvn com.microsoft.azure:azure-webapp-maven-plugin:2.5.0:config
    ```
 
-1. Navigate to the `resources` directory of your app and open `bootstrap.properties` and configure Azure App Configuration Push Refresh.  If the file does not exist, create it. Add the following line to the file.
+1. Navigate to the `resources` directory of your app and open `bootstrap.properties` and configure Azure App Configuration Push Refresh. If the file doesn't exist, create it. Add the following line to the file.
 
     ### [Microsoft Entra ID (recommended)](#tab/entra-id)
     You use the `DefaultAzureCredential` to authenticate to your App Configuration store. Follow the [instructions](./concept-enable-rbac.md#authentication-with-token-credentials) to assign your credential the **App Configuration Data Reader** role. Be sure to allow sufficient time for the permission to propagate before running your application. Create a new file named *AppConfigCredential.java* and add the following lines:
@@ -93,7 +93,7 @@ In this tutorial, you learn how to:
     management.endpoints.web.exposure.include= appconfiguration-refresh
     ```
 
-    Additionally, you need to add the following code to your project, unless you want to use just Managed Identity:
+    Additionally, you need to add the following code to your project, unless you want to use Managed Identity:
 
     ```java
     import org.springframework.stereotype.Component;
@@ -133,7 +133,7 @@ A random delay is added before the cached value is marked as dirty to reduce pot
 
 ## Build and run the app in app service
 
-Event Grid Web Hooks require validation on creation. You can validate by following this [guide](../event-grid/webhook-event-delivery.md) or by starting your application with Azure App Configuration Spring Web Library already configured, which will register your application for you. To use an event subscription, follow the steps in the next two sections.
+Event Grid Web Hooks require validation on creation. You can validate by following this [guide](../event-grid/webhook-event-delivery.md) or by starting your application with Azure App Configuration Spring Web Library already configured, which registers your application for you. To use an event subscription, follow the steps in the next two sections.
 
 1. Set an environment variable.
 
@@ -180,7 +180,7 @@ Event Grid Web Hooks require validation on creation. You can validate by followi
     ```
     ---
 
-    Restart the command prompt to allow the change to take effect. Print the value of the environment variable to validate that it is set properly.
+    Restart the command prompt to allow the change to take effect. Print the value of the environment variable to validate that it's set properly.
 
     ---
 
@@ -210,17 +210,17 @@ Event Grid Web Hooks require validation on creation. You can validate by followi
 
     :::image type="content" source="./media/events-pane.png" alt-text="The events pane has an option to create new Subscriptions." :::
 
-1. Enter a name for the `Event Subscription` and the `System Topic`. By default the Event Types Key-Value modified and Key-Value deleted are set, this can be changed along with using the Filters tab to choose the exact reasons a Push Event will be sent.
+1. Enter a name for the `Event Subscription` and the `System Topic`. By default the Event Types Key-Value modified and Key-Value deleted are set, the reason can be changed along with using the Filters tab to choose the exact reasons a Push Event is sent.
 
     :::image type="content" source="./media/create-event-subscription.png" alt-text="Events require a name, topic, and filters." :::
 
 1. Select the `Endpoint Type` as `Web Hook`, select `Select an endpoint`.
 
     :::image type="content" source="./media/event-subscription-webhook-endpoint.png" alt-text="Selecting Endpoint creates a new blade to enter the endpoint URI." :::
 
-1. The endpoint is the URI of the application + "/actuator/appconfiguration-refresh?{your-token-name}={your-token-secret}". For example `https://my-azure-webapp.azurewebsites.net/actuator/appconfiguration-refresh?myToken=myTokenSecret`
+1. The endpoint is the URI of the application + "/actuator/appconfiguration-refresh?{your-token-name}={your-token-secret}". For example, `https://my-azure-webapp.azurewebsites.net/actuator/appconfiguration-refresh?myToken=myTokenSecret`
 
-1. Select `Create` to create the event subscription. When `Create` is selected a registration request for the Web Hook will be sent to your application. This is received by the Azure App Configuration client library, verified, and returns a valid response.
+1. Select `Create` to create the event subscription. When `Create` is selected, a registration request for the Web Hook is sent to your application. The request is received by the Azure App Configuration client library, verified, and returns a valid response.
 
 1. Select `Event Subscriptions` in the `Events` pane to validate that the subscription was created successfully.
 
@@ -230,7 +230,7 @@ Event Grid Web Hooks require validation on creation. You can validate by followi
 > When subscribing for configuration changes, one or more filters can be used to reduce the number of events sent to your application. These can be configured either as [Event Grid subscription filters](../event-grid/event-filtering.md). For example, a subscription filter can be used to only subscribe to events for changes in a key that starts with a specific string.
 
 > [!NOTE]
-> If you have multiple instances of your application running, you can use the `appconfiguration-refresh-bus` endpoint which requires setting up Azure Service Bus, which is used to send a message to all instances of your application to refresh their configuration. This is useful if you have multiple instances of your application running and want to ensure that all instances are updated with the latest configuration. This endpoint isn't available unless you have `spring-cloud-bus` as a dependency with it configured. See the [Azure Service Bus Spring Cloud Bus documentation](/azure/developer/java/spring-framework/using-service-bus-in-spring-applications) for more information. The service bus connection only needs to be set up and the Azure App Configuration library will handle sending and receiving the messages.
+> If you have multiple instances of your application running, you can use the `appconfiguration-refresh-bus` endpoint which requires setting up Azure Service Bus, which is used to send a message to all instances of your application to refresh their configuration. This is useful if you have multiple instances of your application running and want to ensure that all instances are updated with the latest configuration. This endpoint isn't available unless you have `spring-cloud-bus` as a dependency with it configured. For more information, see [Azure Service Bus Spring Cloud Bus documentation](/azure/developer/java/spring-framework/using-service-bus-in-spring-applications). The service bus connection only needs to be set up and the Azure App Configuration library will handle sending and receiving the messages.
 
 ## Verify and test application
 

articles/azure-app-configuration/quickstart-feature-flag-spring-boot.md

@@ -41,14 +41,14 @@ To create a new Spring Boot project:
 
    * Generate a **Maven** project with **Java**.
    * Specify a **Spring Boot** version that's equal to or greater than 2.0.
-   * Specify the **Group** and **Artifact** names for your application.  This article uses `com.example` and `demo`.
+   * Specify the **Group** and **Artifact** names for your application. This article uses `com.example` and `demo`.
    * Add the **Spring Web** dependency.
 
 1. After you specify the previous options, select **Generate Project**. When prompted, download the project to your local computer.
 
 ## Add feature management
 
-1. After you extract the files on your local system, your Spring Boot application is ready for editing. Locate  *pom.xml* in the root directory of your app.
+1. After you extract the files on your local system, your Spring Boot application is ready for editing. Locate *pom.xml* in the root directory of your app.
 
 1. Open the *pom.xml* file in a text editor and add the following to the list of `<dependencies>`:
 
@@ -85,7 +85,7 @@ To create a new Spring Boot project:
 ## Connect to an App Configuration store
 
 
-1. Navigate to the `resources` directory of your app and open `bootstrap.properties`.  If the file does not exist, create it. Add the following line to the file.
+1. Navigate to the `resources` directory of your app and open `bootstrap.properties`. If the file does not exist, create it. Add the following line to the file.
 
     ### [Microsoft Entra ID (recommended)](#tab/entra-id)
     You use the `DefaultAzureCredential` to authenticate to your App Configuration store. Follow the [instructions](./concept-enable-rbac.md#authentication-with-token-credentials) to assign your credential the **App Configuration Data Reader** role. Be sure to allow sufficient time for the permission to propagate before running your application. Create a new file named *AppConfigCredential.java* and add the following lines:
@@ -95,7 +95,7 @@ To create a new Spring Boot project:
     spring.cloud.azure.appconfiguration.stores[0].feature-flags.enabled=true
     ```
 
-    Additionally, you need to add the following code to your project, unless you want to use just Managed Identity:
+    Additionally, you need to add the following code to your project, unless you want to use Managed Identity:
 
     ```java
     import org.springframework.stereotype.Component;

articles/azure-app-configuration/quickstart-java-spring-app.md

@@ -136,7 +136,7 @@ To use the Spring Cloud Azure Config starter to have your application communicat
     ```
 
 
-1. Open the auto-generated unit test and update to disable Azure App Configuration, or it will try to load from the service when running unit tests.
+1. Open the auto-generated unit test and update to disable Azure App Configuration, or it tries to load from the service when running unit tests.
 
    ```java
    import org.junit.jupiter.api.Test;

articles/azure-app-configuration/use-feature-flags-spring-boot.md

@@ -22,7 +22,7 @@ The Feature Management libraries also manage feature flag lifecycles behind the
 
 The [Add feature flags to a Spring Boot app Quickstart](./quickstart-feature-flag-spring-boot.md) shows several ways to add feature flags in a Spring Boot application. This tutorial explains these methods in more detail.
 
-In this tutorial, you will learn how to:
+In this tutorial, you learn how to:
 
 > [!div class="checklist"]
 > * Add feature flags in key parts of your application to control feature availability.
@@ -174,7 +174,7 @@ public String getOldFeature() {
 
 ## Next steps
 
-In this tutorial, you learned how to implement feature flags in your Spring Boot application by using the `spring-cloud-azure-feature-management-web` libraries.  For further questions see the [reference documentation](https://go.microsoft.com/fwlink/?linkid=2180917), it has all of the details on how the Spring Cloud Azure App Configuration library works.For more information about feature management support in Spring Boot and App Configuration, see the following resources:
+In this tutorial, you learned how to implement feature flags in your Spring Boot application by using the `spring-cloud-azure-feature-management-web` libraries. For further questions see the [reference documentation](https://go.microsoft.com/fwlink/?linkid=2180917). The reference documentation has all of the details on how the Spring Cloud Azure App Configuration library works.For more information about feature management support in Spring Boot and App Configuration, see the following resources:
 
 * [Spring Boot feature flag sample code](./quickstart-feature-flag-spring-boot.md)
 * [Manage feature flags](./manage-feature-flags.md)

articles/azure-app-configuration/use-key-vault-references-spring-boot.md

@@ -17,7 +17,7 @@ In this tutorial, you learn how to use the Azure App Configuration service toget
 
 App Configuration helps you use the services together by creating keys that reference values stored in Key Vault. When App Configuration creates such keys, it stores the URIs of Key Vault values rather than the values themselves.
 
-Your application uses the App Configuration client provider to retrieve Key Vault references, just as it does for any other keys stored in App Configuration. In this case, the values stored in App Configuration are URIs that reference the values in the Key Vault. They are not Key Vault values or credentials. Because the client provider recognizes the keys as Key Vault references, it uses Key Vault to retrieve their values.
+Your application uses the App Configuration client provider to retrieve Key Vault references, just as it does for any other keys stored in App Configuration. In this case, the values stored in App Configuration are URIs that reference the values in the Key Vault. They aren't Key Vault values or credentials. Because the client provider recognizes the keys as Key Vault references, it uses Key Vault to retrieve their values.
 
 Your application is responsible for authenticating properly to both App Configuration and Key Vault. The two services don't communicate directly.
 
@@ -43,7 +43,7 @@ In this tutorial, you learn how to:
 
     ![Screenshot shows the Create a resource option in the Azure portal.](./media/quickstarts/search-services.png)
 1. In the search box, enter **Key Vault**.
-1. From the results list, select **Key vaults** on the left.
+1. From the results list, select **Key vaults**.
 1. In **Key vaults**, select **Add**.
 1. On the right in **Create key vault**, provide the following information:
     * Select **Subscription** to choose a subscription.
@@ -59,7 +59,7 @@ At this point, your Azure account is the only one authorized to access this new
 
 ## Add a secret to Key Vault
 
-To add a secret to the vault, you need to take just a few additional steps. In this case, add a message that you can use to test Key Vault retrieval. The message is called **Message**, and you store the value "Hello from Key Vault" in it.
+To add a secret to the vault, you need to take just a few more steps. In this case, add a message that you can use to test Key Vault retrieval. The message is called **Message**, and you store the value "Hello from Key Vault" in it.
 
 1. From the Key Vault properties pages, select **Secrets**.
 1. Select **Generate/Import**.