revisions

Author: amerjusupovic

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

@@ -232,10 +232,10 @@ The configuration refresh is triggered by the incoming requests to your web app.
 
 ## Monitoring and Troubleshooting
 
-Logs are output upon refresh and contain detailed information on changes to key-values in your App Configuration store and your application, as well as any issues that occur. This allows you to monitor configuration refreshes as they happen. 
+Logs are output upon configuration refresh and contain detailed information on changes to key-values in your App Configuration store and your application.
 
 - A default `ILoggerFactory` is added automatically when `services.AddAzureAppConfiguration()` is invoked in your `ConfigureServices` method. The App Configuration provider uses this `ILoggerFactory` to create an instance of `ILogger`, which outputs these logs. No code changes are needed.
-- Logs are output to the console at different log levels. The default level is `Information`.
+- Logs are output at different log levels. The default level is `Information`.
 
     | Log Level | Description |
     |---|---|
@@ -246,11 +246,10 @@ Logs are output upon refresh and contain detailed information on changes to key-
 - Here is an example `Information` level log:  
   ```console
   info: Microsoft.Extensions.Configuration.AzureAppConfiguration.Refresh[0]
-        Setting updated from Key Vault. Key:'reference'
+      Setting updated from Key Vault. Key:'ExampleKey'
   ```
 
-
-For more information on how to utilize these logs, follow the instructions for [logging in .NET Core and ASP.NET Core](/aspnet/core/fundamentals/logging). Using `ILogger` is the preferred method 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 instructions for [Azure SDK logging for .NET core apps](./enable-dynamic-configuration-dotnet-core.md#monitoring-and-troubleshooting).
+Using `ILogger` is the preferred method 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#monitoring-and-troubleshooting). For more information on how to utilize these logs, follow the instructions for [logging in .NET Core and ASP.NET Core](/aspnet/core/fundamentals/logging).
 
 ## Clean up resources
 

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

@@ -142,9 +142,9 @@ Calling the `ConfigureRefresh` method alone won't cause the configuration to ref
 
 ## Monitoring and Troubleshooting
 
-Logs are output upon refresh and contain detailed information on changes to key-values in your App Configuration store and your application, as well as any issues that occur. This allows you to monitor configuration refreshes as they happen. You can enable these logs using the instructions for [logging with the Azure SDK for .NET](/dotnet/azure/sdk/logging).
+Logs are output upon configuration refresh and contain detailed information on changes to key-values in your App Configuration store and your application. You can enable these logs using the instructions for [logging with the Azure SDK for .NET](/dotnet/azure/sdk/logging).
 
-- Logs are output to the console at different log levels. The default level is `Informational`.
+- Logs are output at different log levels. The default level is `Informational`.
 
     | Log Level | Description |
     |---|---|