Merge pull request #78810 from v-albemi/status-monitor-v2-articles-batch2

edit pass: Status monitor v2 articles batch2

Author: ShawnJackson

articles/azure-monitor/app/status-monitor-v2-api-enable-monitoring.md

@@ -19,7 +19,7 @@ This article describes a cmdlet that's a member of the [Az.ApplicationMonitor Po
 
 > [!IMPORTANT]
 > Status Monitor v2 is currently in public preview.
-> This preview version is provided without a service-level agreement, and we don't recommended it for production workloads. Some features might not be supported, and some might have constrained capabilities.
+> This preview version is provided without a service-level agreement, and we don't recommend it for production workloads. Some features might not be supported, and some might have constrained capabilities.
 > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 ## Description
@@ -39,7 +39,7 @@ After you enable monitoring, we recommend that you use [Live Metrics](live-strea
 > - This cmdlet requires that you review and accept our license and privacy statement.
 
 > [!IMPORTANT] 
-> This cmdlet requires a PowerShell session with Admin permissions and an elevated execution policy. For more information, see [Run PowerShell as administrator with an elevated execution policy](status-monitor-v2-detailed-instructions.md#run-powershell-as-administrator-with-an-elevated-execution-policy).
+> This cmdlet requires a PowerShell session with Admin permissions and an elevated execution policy. For more information, see [Run PowerShell as administrator with an elevated execution policy](status-monitor-v2-detailed-instructions.md#run-powershell-as-admin-with-an-elevated-execution-policy).
 
 ## Examples
 
@@ -103,7 +103,7 @@ The instrumentation engine adds overhead and is off by default.
 **Optional.** Use this switch to accept the license and privacy statement in headless installations.
 
 ### -Verbose
-**Common parameter.** Use this switch to output detailed logs.
+**Common parameter.** Use this switch to display detailed logs.
 
 ### -WhatIf 
 **Common parameter.** Use this switch to test and validate your input parameters without actually enabling monitoring.
@@ -149,7 +149,7 @@ Successfully enabled Application Insights Status Monitor
   View your telemetry:
  - [Explore metrics](../../azure-monitor/app/metrics-explorer.md) to monitor performance and usage.
 - [Search events and logs](../../azure-monitor/app/diagnostic-search.md) to diagnose problems.
-- Use [analytics](../../azure-monitor/app/analytics.md) for more advanced queries.
+- [Use Analytics](../../azure-monitor/app/analytics.md) for more advanced queries.
 - [Create dashboards](../../azure-monitor/app/overview-dashboard.md).
 
  Add more telemetry:

articles/azure-monitor/app/status-monitor-v2-api-set-config.md

@@ -1,6 +1,6 @@
 ---
-title: "Azure Status Monitor v2 API Reference: Set config | Microsoft Docs"
-description: Status Monitor v2 API Reference Set-ApplicationInsightsMonitoringConfig. Monitor website performance without redeploying the website. Works with ASP.NET web apps hosted on-premises, in VMs or on Azure.
+title: "Azure Status Monitor v2 API reference: Set config | Microsoft Docs"
+description: Status Monitor v2 API reference. Set-ApplicationInsightsMonitoringConfig. Monitor website performance without redeploying the website. Works with ASP.NET web apps hosted on-premises, in VMs, or on Azure.
 services: application-insights
 documentationcenter: .net
 author: MS-TimothyMothra
@@ -15,39 +15,39 @@ ms.author: tilee
 ---
 # Status Monitor v2 API: Set-ApplicationInsightsMonitoringConfig (v0.2.1-alpha)
 
-This document describes a cmdlet that's shipped as a member of the [Az.ApplicationMonitor PowerShell module](https://www.powershellgallery.com/packages/Az.ApplicationMonitor/).
+This document describes a cmdlet that's a member of the [Az.ApplicationMonitor PowerShell module](https://www.powershellgallery.com/packages/Az.ApplicationMonitor/).
 
 > [!IMPORTANT]
 > Status Monitor v2 is currently in public preview.
-> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
-> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
+> This preview version is provided without a service-level agreement, and we don't recommend it for production workloads. Some features might not be supported, and some might have constrained capabilities.
+> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 ## Description
 
-Set the config file without repeating a full reinstall. 
+Sets the config file without doing a full reinstallation.
 Restart IIS for your changes to take effect.
 
 > [!IMPORTANT] 
-> This cmdlet requires a PowerShell Session with Administrator permissions.
+> This cmdlet requires a PowerShell session with Admin permissions.
 
 
 ## Examples
 
-### Example with single instrumentation key
-In this example, all applications on the current machine will be assigned a single instrumentation key.
+### Example with a single instrumentation key
+In this example, all apps on the current computer will be assigned a single instrumentation key.
 
 ```powershell
 PS C:\> Enable-ApplicationInsightsMonitoring -InstrumentationKey xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
 ```
 
-### Example with instrumentation key map
-In this example, 
-- `MachineFilter` will match the current machine using the `'.*'` wildcard.
-- `AppFilter='WebAppExclude'` provides a `null` InstrumentationKey. This app won't be instrumented.
-- `AppFilter='WebAppOne'` will assign this specific app a unique instrumentation key.
-- `AppFilter='WebAppTwo'` will also assign this specific app a unique instrumentation key.
-- Lastly, `AppFilter` also uses the `'.*'` wildcard to match all other web apps not matched by the earlier rules and assigns a default instrumentation key.
-- Spaces added for readability only.
+### Example with an instrumentation key map
+In this example:
+- `MachineFilter` matches the current computer by using the `'.*'` wildcard.
+- `AppFilter='WebAppExclude'` provides a `null` instrumentation key. The specified app won't be instrumented.
+- `AppFilter='WebAppOne'` assigns the specified app a unique instrumentation key.
+- `AppFilter='WebAppTwo'` assigns the specified app a unique instrumentation key.
+- Finally, `AppFilter` also uses the `'.*'` wildcard to match all web apps that aren't matched by the earlier rules and assign a default instrumentation key.
+- Spaces are added for readability.
 
 ```powershell
 PS C:\> Enable-ApplicationInsightsMonitoring -InstrumentationKeyMap 
@@ -59,38 +59,38 @@ PS C:\> Enable-ApplicationInsightsMonitoring -InstrumentationKeyMap
 ```
 
 
-## Parameters 
+## Parameters
 
 ### -InstrumentationKey
-**Required.** Use this parameter to supply a single iKey for use by all applications on the target machine.
+**Required.** Use this parameter to supply a single instrumentation key for use by all apps on the target computer.
 
 ### -InstrumentationKeyMap
-**Required.** Use this parameter to supply multiple ikeys and a mapping of which apps to use which ikey. 
-You can create a single installation script for several machines by setting the MachineFilter. 
+**Required.** Use this parameter to supply multiple instrumentation keys and a mapping of the instrumentation keys used by each app.
+You can create a single installation script for several computers by setting `MachineFilter`.
 
-> [!IMPORTANT] 
-> Applications will match against rules in the order that they're provided. As such you should specify the most specific rules first and the most generic rules last.
+> [!IMPORTANT]
+> Apps will match against rules in the order that the rules are provided. So you should specify the most specific rules first and the most generic rules last.
 
 #### Schema
 `@(@{MachineFilter='.*';AppFilter='.*';InstrumentationKey='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'})`
 
-- **MachineFilter** is a required c# regex of the computer or vm name.
+- **MachineFilter** is a required C# regex of the computer or VM name.
 	- '.*' will match all
-	- 'ComputerName' will match only computers with that exact name.
-- **AppFilter** is a required c# regex of the computer or vm name.
+	- 'ComputerName' will match only computers with the specified name.
+- **AppFilter** is a required C# regex of the computer or VM name.
 	- '.*' will match all
-	- 'ApplicationName' will match only IIS applications with that exact name.
-- **InstrumentationKey** is required to enable monitoring of the applications that match the above two filters.
-	- Leave this value null if you wish to define rules to exclude monitoring
+	- 'ApplicationName' will match only IIS apps with the specified name.
+- **InstrumentationKey** is required to enable monitoring of the apps that match the preceding two filters.
+	- Leave this value null if you want to define rules to exclude monitoring.
 
 
 ### -Verbose
-**Common Parameter.** Use this switch to output detailed logs.
+**Common parameter.** Use this switch to display detailed logs.
 
 
 ## Output
 
-No Output by default.
+By default, no output.
 
 #### Example verbose output from setting the config file via -InstrumentationKey
 
@@ -121,17 +121,17 @@ C:\Program Files\WindowsPowerShell\Modules\Az.ApplicationMonitor\content\applica
 ## Next steps
 
   View your telemetry:
- - [Explore metrics](../../azure-monitor/app/metrics-explorer.md) to monitor performance and usage
-- [Search events and logs](../../azure-monitor/app/diagnostic-search.md) to diagnose problems
-- [Analytics](../../azure-monitor/app/analytics.md) for more advanced queries
-- [Create dashboards](../../azure-monitor/app/overview-dashboard.md)
+ - [Explore metrics](../../azure-monitor/app/metrics-explorer.md) to monitor performance and usage.
+- [Search events and logs](../../azure-monitor/app/diagnostic-search.md) to diagnose problems.
+- [Use Analytics](../../azure-monitor/app/analytics.md) for more advanced queries.
+- [Create dashboards](../../azure-monitor/app/overview-dashboard.md).
 
  Add more telemetry:
  - [Create web tests](monitor-web-app-availability.md) to make sure your site stays live.
-- [Add web client telemetry](../../azure-monitor/app/javascript.md) to see exceptions from web page code and to let you insert trace calls.
-- [Add Application Insights SDK to your code](../../azure-monitor/app/asp-net.md) so that you can insert trace and log calls
+- [Add web client telemetry](../../azure-monitor/app/javascript.md) to see exceptions from web page code and to enable trace calls.
+- [Add the Application Insights SDK to your code](../../azure-monitor/app/asp-net.md) so you can insert trace and log calls
 
  Do more with Status Monitor v2:
- - Use our guide to [Troubleshoot](status-monitor-v2-troubleshoot.md) Status Monitor v2.
+ - Use our guide to [troubleshoot](status-monitor-v2-troubleshoot.md) Status Monitor v2.
  - [Get the config](status-monitor-v2-api-get-config.md) to confirm that your settings were recorded correctly.
  - [Get the status](status-monitor-v2-api-get-status.md) to inspect monitoring.