Update

Author: RichardChen820

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

@@ -372,11 +372,11 @@ Ensure that you specify the correct key-value selectors to match the expected da
 
 You can customize the installation by providing additional Helm values when installing the Azure App Configuration Kubernetes Provider. For example, you can set the log level, configure the provider to run on a specific node, or disable the workload identity. Refer to the [installation guide](./reference-kubernetes-provider.md#installation) for more information.
 
-#### How can I refresh ConfigMap on demand rather than waiting for the periodic refresh?
+#### How to trigger on-demand refresh of ConfigMap and Secret
 
-If you make any changes to the `spec` of the `AzureAppConfigurationProvider` resource, the Azure App Configuration provider will reconcile and update the configMap with the most recent data from the Azure App Configuration store.
+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 restart the deployment of the Azure App Configuration Kubernetes provider controller. The Kubernetes provider will then reconcile and update the ConfigMap and Secret with the latest data from your App Configuration store and Key Vault.
 
-If you don’t modify your `AzureAppConfigurationProvider` resource, since the Azure App Configuration provider controller reconciles all `AzureAppConfigurationProvider` resources on each time it starts, you just need to restart the deployment of the Azure App Configuration provider controller to trigger an on demand refresh. Please note that this will cause all `AzureAppConfigurationProvider` resources on the cluster to be reconciled to resynchronizing with Azure App Configuration stores.
+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.
 
 #### Why am I unable to authenticate with Azure App Configuration using workload identity after upgrading the provider to version 2.0.0?