udpate reference doc

Author: linglingye001

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

@@ -383,9 +383,9 @@ spec:
 
 ### Configuration refresh
 
-When you make changes to your data in Azure App Configuration, you might want those changes to be refreshed automatically in your Kubernetes cluster. It's common to update multiple key-values, but you don't want the cluster to pick up a change midway through the update. To maintain configuration consistency, you can use a key-value to signal the completion of your update. This key-value is known as the sentinel key. The Kubernetes provider can monitor this key-value, and the ConfigMap and Secret will only be regenerated with updated data once a change is detected in the sentinel key.
+When you make changes to your data in Azure App Configuration, you might want those changes to be refreshed automatically in your Kubernetes cluster. 
 
-In the following sample, a key-value named `app1_sentinel` is polled every minute, and the configuration is refreshed whenever changes are detected in the sentinel key.
+In the following sample, the Kubernetes provider makes a new request to App Configuration to check for any configuration changes every minute, and the ConfigMap and Secret will only be regenerated with updated data once a change is detected. For more information about monitoring configuration changes, see [Best practices for configuration refresh](./howto-best-practices.md#configuration-refresh).
 
 ``` yaml
 apiVersion: azconfig.io/v1
@@ -403,10 +403,6 @@ spec:
     refresh:
       enabled: true
       interval: 1m
-      monitoring:
-        keyValues:
-          - key: app1_sentinel
-            label: common
 ```
 
 ### Key Vault references