Updated as per �Peer Review Feedback

Author: v-niranjan

articles/azure-monitor/profiler/profiler-bring-your-own-storage.md

@@ -16,13 +16,13 @@ ms.custom: devdivchpfy22
 
 When you use Application Insights Profiler or Snapshot Debugger, artifacts generated by your application are uploaded into Azure storage accounts over the public Internet. For these artifacts and storage accounts, Microsoft controls and covers the cost for:
 
-* Processing and analysis
-* Encryption-at-rest and lifetime management policies
+* Processing and analysis.
+* Encryption-at-rest and lifetime management policies.
 
 When you configure Bring Your Own Storage (BYOS), artifacts are uploaded into a storage account that you control. That means you control and are responsible for the cost of:
 
-* The encryption-at-rest policy and the Lifetime management policy
-* Network access
+* The encryption-at-rest policy and the Lifetime management policy.
+* Network access.
 
 > [!NOTE]
 > BYOS is required if you are enabling Private Link or Customer-Managed Keys.
@@ -79,19 +79,19 @@ Steps:
     :::image type="content" source="media/profiler-bring-your-own-storage/add-role-assignment-page.png" alt-text="Screenshot showing how to add role assignment page in Azure portal.":::
     *Figure 1.0*
 
-After you added the role, it will appear under the "Role assignments" section, like the below Figure 1.1.
+After you added the role, it will appear under the "**Role assignments**" section, like the below Figure 1.1.
     :::image type="content" source="media/profiler-bring-your-own-storage/figure-11.png" alt-text="Screenshot showing the IAM screen after Role assignments.":::
     *Figure 1.1*
 
-If you're also using Private Link, it's required one additional configuration to allow connection to our Trusted Microsoft Service from your Virtual Network. Refer to the [Storage Network Security documentation](../../storage/common/storage-network-security.md#trusted-microsoft-services).
+If you're also using Private Link, it's required one additional configuration to allow connection to our Trusted Microsoft Service from your Virtual Network. or more information, see [Storage Network Security documentation](../../storage/common/storage-network-security.md#trusted-microsoft-services).
 
 ### Link your Storage Account with your Application Insights resource
 
 To configure BYOS for code-level diagnostics (Profiler/Debugger), there are three options:
 
-* Using Azure PowerShell cmdlets
-* Using the Azure CLI
-* Using Azure Resource Manager templates
+* Using Azure PowerShell cmdlets.
+* Using the Azure CLI.
+* Using Azure Resource Manager templates.
 
 #### [PowerShell](#tab/azure-powershell)
 
@@ -111,7 +111,7 @@ To configure BYOS for code-level diagnostics (Profiler/Debugger), there are thre
     Connect-AzAccount -Subscription "{subscription_id}"
     ```
 
-    For more info of how to sign in, refer to the [Connect-AzAccount documentation](/powershell/module/az.accounts/connect-azaccount).
+    For more information on how to sign in, refer to the [Connect-AzAccount documentation](/powershell/module/az.accounts/connect-azaccount).
 
 1. Remove previous Storage Account linked to your Application Insights resource.
 

articles/azure-monitor/snapshot-debugger/snapshot-debugger-app-service.md

@@ -14,13 +14,13 @@ ms.custom: devdivchpfy22
 
 Snapshot Debugger currently supports ASP.NET and ASP.NET Core apps that are running on Azure App Service on Windows service plans.
 
-We recommend you run your application on the Basic service tier, or higher, when using Snapshot Debugger.
+We recommend that you run your application on the Basic service tier, or higher, when using Snapshot Debugger.
 
 For most applications, the Free and Shared service tiers don't have enough memory or disk space to save snapshots.
 
 ## <a id="installation"></a> Enable Snapshot Debugger
 
-Snapshot Debugger is pre-installed as part of the App Services runtime, but you need to turn it on to get snapshots for your App Service app. To enable Snapshot Debugger for an app, follow the instructions below.
+Snapshot Debugger is pre-installed as part of the App Services runtime, but you need to turn it on to get snapshots for your App Service app. To enable Snapshot Debugger for an app, follow the instructions below:
 
 > [!NOTE]
 > If you're using a preview version of .NET Core, or your application references Application Insights SDK (directly or indirectly via a dependent assembly), follow the instructions for [Enable Snapshot Debugger for other environments](snapshot-debugger-vm.md) to include the [`Microsoft.ApplicationInsights.SnapshotCollector`](https://www.nuget.org/packages/Microsoft.ApplicationInsights.SnapshotCollector) NuGet package with the application.
@@ -29,9 +29,9 @@ Snapshot Debugger is pre-installed as part of the App Services runtime, but you
 > Codeless installation of Application Insights Snapshot Debugger follows the .NET Core support policy.
 > For more information about supported runtimes, see [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
 
-Once you've deployed your .NET app:
+After you've deployed your .NET app:
 
-1. Navigate to the Azure control panel for your App Service.
+1. Go to to the Azure control panel for your App Service.
 1. Go to the **Settings** > **Application Insights** page.
 
    :::image type="content" source="./media/snapshot-debugger/application-insights-app-services.png" alt-text="Screenshot showing the Enable App Insights on App Services portal.":::
@@ -69,15 +69,15 @@ Application Insights Snapshot Debugger supports Azure AD authentication for snap
 
 As of today, Snapshot Debugger only supports Azure AD authentication when you reference and configure Azure AD using the Application Insights SDK in your application.
 
-To enable Azure AD for snapshot ingestion:
+To turn-on Azure AD for snapshot ingestion:
 
 1. Create and add the managed identity you want to use to authenticate against your Application Insights resource to your App Service.
 
-    1. For System-Assigned Managed identity, see the following [documentation](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-system-assigned-identity)
+    1. For System-Assigned Managed identity, see the following [documentation](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-system-assigned-identity).
 
-    1. For User-Assigned Managed identity, see the following [documentation](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-user-assigned-identity)
+    1. For User-Assigned Managed identity, see the following [documentation](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-user-assigned-identity).
 
-1. Configure and enable Azure AD in your Application Insights resource. For more information, see the following [documentation](../app/azure-ad-authentication.md?tabs=net#configuring-and-enabling-azure-ad-based-authentication)
+1. Configure and turn on Azure AD in your Application Insights resource. For more information, see the following [documentation](../app/azure-ad-authentication.md?tabs=net#configuring-and-enabling-azure-ad-based-authentication)
 1. Add the following application setting, used to let Snapshot Debugger agent know which managed identity to use:
 
 For System-Assigned Identity:
@@ -94,7 +94,7 @@ For User-Assigned Identity:
 
 ## Disable Snapshot Debugger
 
-To disable Snapshot Debugger, repeat the [steps for enabling](#installation), but switch the Snapshot Debugger toggles to **Off**.
+To disable Snapshot Debugger, repeat the [steps for enabling](#installation). However, switch the Snapshot Debugger toggles to **Off**.
 
 ## Azure Resource Manager template
 
@@ -140,11 +140,11 @@ For an Azure App Service, you can set app settings within the Azure Resource Man
 
 ## Not Supported Scenarios
 
-Below you can find scenarios where Snapshot Collector is not supported:
+Below you can find scenarios where Snapshot Collector isn't supported:
 
 |Scenario    | Side Effects | Recommendation |
 |------------|--------------|----------------|
-|You're using the Snapshot Collector SDK in your application directly (.csproj) and have enabled the advanced option "Interop".| The local Application Insights SDK (including Snapshot Collector telemetry) will be lost and no Snapshots will be available. <br/> Your application could crash at startup with `System.ArgumentException: telemetryProcessorTypedoes not implement ITelemetryProcessor.` <br/> [Learn more about the Application Insights feature "Interop".](../app/azure-web-apps-net-core.md#troubleshooting) | If you are using the advanced option "Interop", use the codeless Snapshot Collector injection (enabled through the Azure portal). |
+|You're using the Snapshot Collector SDK in your application directly (*.csproj*) and have enabled the advanced option "Interop".| The local Application Insights SDK (including Snapshot Collector telemetry) will be lost and no Snapshots will be available. <br/> Your application could crash at startup with `System.ArgumentException: telemetryProcessorTypedoes not implement ITelemetryProcessor.` <br/> [Learn more about the Application Insights feature "Interop".](../app/azure-web-apps-net-core.md#troubleshooting) | If you're using the advanced option "Interop", use the codeless Snapshot Collector injection (enabled through the Azure portal). |
 
 ## Next steps
 

articles/azure-monitor/snapshot-debugger/snapshot-debugger-function-app.md

@@ -14,7 +14,7 @@ ms.custom: devdivchpfy22
 
 Snapshot Debugger currently works for ASP.NET and ASP.NET Core apps that are running on Azure Functions on Windows Service Plans.
 
-We recommend you run your application on the Basic service tier or higher when using Snapshot Debugger.
+We recommend that you run your application on the Basic service tier or higher when using Snapshot Debugger.
 
 For most applications, the Free and Shared service tiers don't have enough memory or disk space to save snapshots.
 
@@ -43,7 +43,7 @@ Snapshot Debugger is pre-installed as part of the Azure Functions runtime and is
 
 In the simple .NET Core Function app example below, `.csproj`, `{Your}Function.cs`, and `host.json` has Snapshot Debugger enabled:
 
-***Project.`csproj`***
+***`Project.csproj`***
 
 ```xml
 <Project Sdk="Microsoft.NET.Sdk">
@@ -160,11 +160,11 @@ To disable Snapshot Debugger in your Function app, update your `host.json` file
 }
 ```
 
-We recommend you have Snapshot Debugger enabled on all your apps to ease diagnostics of application exceptions.
+We recommend that you have Snapshot Debugger enabled on all your apps to ease diagnostics of application exceptions.
 
 ## Next steps
 
 * Generate traffic to your application that can trigger an exception. Then, wait 10 to 15 minutes for snapshots to be sent to the Application Insights instance.
 * [View snapshots](snapshot-debugger.md?toc=/azure/azure-monitor/toc.json#view-snapshots-in-the-portal) in the Azure portal.
-* Customize Snapshot Debugger configuration based on your use-case on your Function app. For more info, see [snapshot configuration in host.json](../../azure-functions/functions-host-json.md#applicationinsightssnapshotconfiguration).
+* Customize Snapshot Debugger configuration based on your use-case on your Function app. For more information, see [snapshot configuration in host.json](../../azure-functions/functions-host-json.md#applicationinsightssnapshotconfiguration).
 * For help with troubleshooting Snapshot Debugger issues, see [Snapshot Debugger troubleshooting](snapshot-debugger-troubleshoot.md?toc=/azure/azure-monitor/toc.json).