update

Author: linglingye001

articles/azure-app-configuration/quickstart-azure-kubernetes-service.md

@@ -383,7 +383,7 @@ Use the logs for further troubleshooting. Refer to the [FAQ](#faq) section for c
 
 ## FAQ
 
-#### Why isn’t the ConfigMap or Secret being generated?
+#### Why isn't the ConfigMap or Secret being generated?
 
 You can follow the steps in the [Troubleshooting](#troubleshooting) guide to collect logs for detailed error information. Here are some common causes.
 
@@ -400,7 +400,7 @@ You can customize the installation by providing additional Helm values when inst
 
 #### How to trigger on-demand refresh of ConfigMap and Secret
 
-While you can set up automatic data refresh, there are times when you might want to trigger an on-demand refresh to get the latest data from App Configuration and Key Vault. To do this, you can modify `metadata.annotations` section and apply the changes. The Kubernetes provider will then reconcile and update the ConfigMap and Secret with the latest data from your App Configuration store and Key Vault. For examples and more information, see [On-demand Refresh](./reference-kubernetes-provider.md#on-demand-refresh).
+To do this, you can modify the `metadata.annotations` section of `AzureAppConfigurationProvider`. The Kubernetes provider will then reconcile and update the ConfigMap and Secret with the latest data from your App Configuration store and Key Vault. See [On-demand Refresh](./reference-kubernetes-provider.md#on-demand-refresh) for an example.
 
 It is not recommended to delete or modify the ConfigMap and Secret generated by the Kubernetes provider. Although new ones will be generated from the latest data, this could cause downtime for your applications in the event of any failures.
 

articles/azure-app-configuration/reference-kubernetes-provider.md

@@ -554,7 +554,7 @@ spec:
 
 While you can set up automatic data refresh, there are times when you might want to trigger an on-demand refresh to get the latest data from App Configuration and Key Vault. This can be done by adding or updating arbitrary key-value pairs of type `string` in the `metadata.annotations` section. The Kubernetes provider will then reconcile and update the ConfigMap and Secret with the latest data from your App Configuration store and Key Vault.
 
-The following example modifies the `annotations` of `AzureAppConfigurationProvider` with a new key-value pair. After updating the annotations, apply the changes using `kubectl apply` to trigger on-demand refresh.
+In the following example, the `annotations` of `AzureAppConfigurationProvider` are updated with a new key-value pair. After modifying the annotations, apply the changes using `kubectl apply` to trigger an on-demand refresh.
 
 ``` yaml
 apiVersion: azconfig.io/v1