Addressing Zhenlan's feedback and a few other tweaks

Author: lisaguthrie

articles/azure-app-configuration/enable-dynamic-configuration-aspnet-core.md

@@ -77,10 +77,10 @@ A *sentinel key* is a special key used to signal when configuration has changed.
                 config.AddAzureAppConfiguration(options =>
                 {
                     options.Connect(settings["ConnectionStrings:AppConfig"])
-                            .ConfigureRefresh(refresh =>
+                           .ConfigureRefresh(refresh =>
                                 {
                                     refresh.Register("TestApp:Settings:Sentinel", refreshAll: true)
-                                            .SetCacheExpiration(new TimeSpan(0, 0, 1));
+                                           .SetCacheExpiration(new TimeSpan(0, 5, 0));
                                 });
                 });
             })
@@ -97,27 +97,27 @@ A *sentinel key* is a special key used to signal when configuration has changed.
                 {
                     var settings = config.Build();
                     config.AddAzureAppConfiguration(options =>
-                    {   
+                    {
                         options.Connect(settings["ConnectionStrings:AppConfig"])
-                                .ConfigureRefresh(refresh =>
+                               .ConfigureRefresh(refresh =>
                                     {
                                         refresh.Register("TestApp:Settings:Sentinel", refreshAll: true)
-                                               .SetCacheExpiration(new TimeSpan(0, 0, 1));
+                                               .SetCacheExpiration(new TimeSpan(0, 5, 0));
                                     });
                     });
                 })
             .UseStartup<Startup>());
     ```
     ---
 
-    The `ConfigureRefresh` method is used to specify the settings used to update the configuration data with the App Configuration store when a refresh operation is triggered. The `refreshAll` parameter to the `Register` method indicates that all configuration values should be refreshed if the sentinel key changes. 
-    
-    Also, the `SetCacheExpiration` method overrides the default cache expiration time of 30 seconds, specifying a time of 1 second instead.
+    The `ConfigureRefresh` method is used to specify the settings used to update the configuration data with the App Configuration store when a refresh operation is triggered. The `refreshAll` parameter to the `Register` method indicates that all configuration values should be refreshed if the sentinel key changes.
 
-    > [!WARNING]
-    > Use higher cache expiration times in production to avoid unnecessary requests to App Configuration.
-    
-    To actually trigger a refresh operation, configure a refresh middleware for the application to refresh the configuration data when any change occurs.
+    Also, the `SetCacheExpiration` method overrides the default cache expiration time of 30 seconds, specifying a time of 5 minutes instead. This reduces the number of requests made to App Configuration.
+
+    > [!NOTE]
+    > For testing purposes, you may want to lower the cache expiration time.
+
+    To actually trigger a refresh operation, you'll need to configure a refresh middleware for the application to refresh the configuration data when any change occurs. You'll see how to do this in step #4.
 
 2. Add a *Settings.cs* file that defines and implements a new `Settings` class.
 
@@ -312,7 +312,7 @@ A *sentinel key* is a special key used to signal when configuration has changed.
 1. After the build successfully completes, run the following command to run the web app locally:
 
         dotnet run
-1. Open a browser window, and go to `http://localhost:5000`, which is the default URL for the web app hosted locally.
+1. Open a browser window, and go to the URL shown in the `dotnet run` output.
 
     ![Launching quickstart app locally](./media/quickstarts/aspnet-core-app-launch-local-before.png)
 

articles/azure-app-configuration/faq.md

@@ -95,9 +95,22 @@ You can't downgrade a store from the Standard tier to the Free tier. You can cre
 
 ## Are there any limits on the number of requests made to App Configuration?
 
-Configuration stores in the Free tier are limited to 1,000 requests per day. Configuration stores in the Standard tier may experience temporary throttling when the request rate exceeds 20,000 requests per hour. When a store reaches its limit, it will return HTTP status code 429 for all requests made until the time period expires.
+Configuration stores in the Free tier are limited to 1,000 requests per day. Configuration stores in the Standard tier may experience temporary throttling when the request rate exceeds 20,000 requests per hour.
 
-If your application regularly experiences HTTP status code 429, consider redesigning it to reduce the number of requests made. For more information, see [Reduce requests made to App Configuration](./howto-best-practices.md#reduce-requests-made-to-app-configuration)
+When a store reaches its limit, it will return HTTP status code 429 for all requests made until the time period expires. The `retry-after-ms` header in the response gives a suggested wait time (in milliseconds) before retrying the request.
+
+If your application regularly experiences HTTP status code 429 responses, consider redesigning it to reduce the number of requests made. For more information, see [Reduce requests made to App Configuration](./howto-best-practices.md#reduce-requests-made-to-app-configuration)
+
+## My application receives HTTP status code 429 responses. Why?
+
+You'll receive an HTTP status code 429 response under these circumstances:
+
+* Exceeding the daily request limit for a store in the Free tier.
+* Temporary throttling due to a high request rate for a store in the Standard tier.
+* Excessive bandwidth usage.
+* Attempting to create or modify a key when the storage quote is exceeded.
+
+Check the body of the 429 response for the specific reason why the request failed.
 
 ## How can I receive announcements on new releases and other information related to App Configuration?
 

articles/azure-app-configuration/howto-best-practices.md

@@ -69,12 +69,14 @@ You can provide access to App Configuration for web apps or functions by using a
 
 ## Reduce requests made to App Configuration
 
-If your application consistently experiences HTTP status code 429, consider redesigning it to reduce the number of requests made.
+Excessive requests to App Configuration can result in throttling or overage charges. To reduce the number of requests made:
 
 * Increase the refresh timeout, especially if your configuration values do not change frequently. Specify a new refresh timeout using the [`SetCacheExpiration` method](/dotnet/api/microsoft.extensions.configuration.azureappconfiguration.azureappconfigurationrefreshoptions.setcacheexpiration).
 
 * Watch a single *sentinel key*, rather than watching individual keys. Refresh all configuration only if the sentinel key changes. See [Use dynamic configuration in an ASP.NET Core app](enable-dynamic-configuration-aspnet-core.md) for an example.
 
+* Use Azure Event Grid to receive notifications when configuration changes, rather than constantly polling for any changes. See [Route Azure App Configuration events to a web endpoint](./howto-app-configuration-event) for more information
+
 ## Next steps
 
 * [Keys and values](./concept-key-value.md)