add aspnet revisions to dotnet doc, clarify 6.0.0 version

Author: amerjusupovic

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

@@ -230,7 +230,7 @@ The configuration refresh is triggered by the incoming requests to your web app.
 
     ![Launching updated quickstart app locally](./media/quickstarts/aspnet-core-app-launch-local-after.png)
 
-## Logging and Monitoring (v6.0.0 and later)
+## Logging and Monitoring
 
 Logs are output upon configuration refresh and contain detailed information on key-values retrieved from your App Configuration store and configuration changes made to your application.
 
@@ -264,9 +264,11 @@ Logs are output upon configuration refresh and contain detailed information on k
     Service request failed.
     ```
 
-
 Using `ILogger` is the preferred method in ASP.NET applications and is prioritized as the logging source if an instance of `ILoggerFactory` is present. However, if `ILoggerFactory` is not available, logs can alternatively be enabled and configured through the [instructions for .NET Core apps](./enable-dynamic-configuration-dotnet-core.md#logging-and-monitoring-v600-and-later). For more information, see [logging in .NET Core and ASP.NET Core](/aspnet/core/fundamentals/logging).
 
+> [!NOTE]
+> Logging is available if you use version **6.0.0** or later of the `Microsoft.Extensions.Configuration.AzureAppConfiguration` package.
+
 ## Clean up resources
 
 [!INCLUDE [azure-app-configuration-cleanup](../../includes/azure-app-configuration-cleanup.md)]

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

@@ -151,8 +151,18 @@ Logs are output upon configuration refresh and contain detailed information on k
     | Verbose | Logs include the key and label of key-values your application monitors for changes from your App Configuration store. The information also includes whether the key-value has changed compared with what your application has already loaded. Enable logs at this level to troubleshoot your application if a configuration change didn't happen as expected. |
     | Informational | Logs include the keys of configuration settings updated during a configuration refresh. Values of configuration settings are omitted from the log to avoid leaking sensitive data. You can monitor logs at this level to ensure your application picks up expected configuration changes. |
     | Warning | Logs include failures and exceptions that occurred during configuration refresh. Occasional occurrences can be ignored because the configuration provider will continue using the cached data and attempt to refresh the configuration next time. You can monitor logs at this level for repetitive warnings that may indicate potential issues. For example, you rotated the connection string but forgot to update your application. |
-- The logging category is `Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh`, which appears before each log.
-- Here are some example logs at each event level: 
+
+    You can enable logging at the `Verbose` event level by specifying the `EventLevel.Verbose` parameter, as done in the following example. These instructions apply to all other event levels as well. This example also enables logs for only the `Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh` category.
+    ```csharp
+    using var listener = new AzureEventSourceListener((eventData, text) =>
+    {
+        if (eventData.EventSource.Name == "Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh")
+        {
+            Console.WriteLine("[{1}] {0}: {2}", eventData.EventSource.Name, eventData.Level, text);
+        }
+    }, EventLevel.Verbose);
+    ```
+- The logging category is `Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh`, which appears before each log. Here are some example logs at each event level: 
     ```console
     [Verbose] Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh:
     Key-value read from App Configuration. Change:'Modified' Key:'ExampleKey' Label:'ExampleLabel' Endpoint:'https://examplestore.azconfig.io'
@@ -164,16 +174,9 @@ Logs are output upon configuration refresh and contain detailed information on k
     A refresh operation failed.
     Service request failed.
     ```
-- You can enable logging at the `Verbose` event level by specifying the `EventLevel.Verbose` parameter, as done in the following example. These instructions apply to all other event levels as well. This example also enables logs for only the `Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh` category.
-    ```csharp
-    using var listener = new AzureEventSourceListener((eventData, text) =>
-    {
-        if (eventData.EventSource.Name == "Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh")
-        {
-            Console.WriteLine("[{1}] {0}: {2}", eventData.EventSource.Name, eventData.Level, text);
-        }
-    }, EventLevel.Verbose);
-    ```
+
+> [!NOTE]
+> Logging is available if you use version **6.0.0** or later of the `Microsoft.Extensions.Configuration.AzureAppConfiguration` package.
 
 ## Clean up resources