edit pass: app-articles-batch-18

paulth1 · paulth1 · commit e225c4419188 · 2023-01-30T17:40:37.000-08:00
diff --git a/articles/azure-monitor/app/azure-ad-authentication.md b/articles/azure-monitor/app/azure-ad-authentication.md
@@ -33,7 +33,6 @@ The following SDKs and features are unsupported for use with Azure AD authentica
  Azure AD authentication is only available for Application Insights Java Agent greater than or equal to 3.2.0.
 - [ApplicationInsights JavaScript web SDK](javascript.md).
 - [Application Insights OpenCensus Python SDK](opencensus-python.md) with Python version 3.4 and 3.5.
-
 - [Certificate/secret-based Azure AD](../../active-directory/authentication/active-directory-certificate-based-authentication-get-started.md) isn't recommended for production. Use Managed Identities instead.
 - On-by-default codeless monitoring (for languages) for Azure App Service, Azure Virtual Machines/Azure Virtual Machine Scale Sets, and Azure Functions.
 - [Availability tests](availability-overview.md).
@@ -145,11 +144,11 @@ appInsights.defaultClient.config.aadTokenCredential = credential;
     > [!IMPORTANT]
     > Use the full connection string, which includes `IngestionEndpoint`, when you configure your app with the Java agent. For example, use `InstrumentationKey=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX;IngestionEndpoint=https://XXXX.applicationinsights.azure.com/`.
 
-    > [!NOTE]
-    >  For more information about migrating from the 2.X SDK to the 3.X Java agent, see [Upgrading from Application Insights Java 2.x SDK](java-standalone-upgrade-from-2x.md).
-
 1. Add the JSON configuration to the *ApplicationInsights.json* configuration file depending on the authentication you're using. We recommend using managed identities.
 
+> [!NOTE]
+>  For more information about migrating from the 2.X SDK to the 3.X Java agent, see [Upgrading from Application Insights Java 2.x SDK](java-standalone-upgrade-from-2x.md).
+
 #### System-assigned managed identity
 
 The following example shows how to configure the Java agent to use system-assigned managed identity for authentication with Azure AD.
diff --git a/articles/azure-monitor/app/data-model-request-telemetry.md b/articles/azure-monitor/app/data-model-request-telemetry.md
@@ -32,7 +32,7 @@ ID is the identifier of a request call instance. It's used for correlation betwe
 
 ## URL
 
-The request URL with all query string parameters.
+URL is the request URL with all query string parameters.
 
 **Maximum length**: 2,048 characters
 
@@ -56,7 +56,7 @@ The response code is the result of a request execution. It's the HTTP status cod
 
 Success indicates whether a call was successful or unsuccessful. This field is required. When a request isn't set explicitly to `false`, it's considered to be successful. Set this value to `false` if the operation was interrupted by an exception or a returned error result code.
 
-For web applications, Application Insights define a request as successful when the response code is less than `400` or equal to `401`. However, there are cases when this default mapping doesn't match the semantics of the application.
+For web applications, Application Insights defines a request as successful when the response code is less than `400` or equal to `401`. However, there are cases when this default mapping doesn't match the semantics of the application.
 
 Response code `404` might indicate "no records," which can be part of regular flow. It also might indicate a broken link. For broken links, you can implement more advanced logic. You can mark broken links as failures only when those links are located on the same site by analyzing the URL referrer. Or you can mark them as failures when they're accessed from the company's mobile application. Similarly, `301` and `302` indicate failure when they're accessed from the client that doesn't support redirect.
 
@@ -75,6 +75,6 @@ You can read more about the request result code and status code in the [blog pos
 ## Next steps
 
 - [Write custom request telemetry](./api-custom-events-metrics.md#trackrequest).
-- See [data model](data-model.md) for Application Insights types and data model.
+- See the [data model](data-model.md) for Application Insights types and data models.
 - Learn how to [configure an ASP.NET Core](./asp-net.md) application with Application Insights.
 - Check out [platforms](./app-insights-overview.md#supported-languages) supported by Application Insights.
diff --git a/articles/azure-monitor/app/live-stream.md b/articles/azure-monitor/app/live-stream.md
@@ -171,7 +171,7 @@ If you want to monitor a particular server role instance, you can filter by serv
 
 Live Metrics custom filters allow you to control which of your application's telemetry is streamed to the Live Metrics view in the Azure portal. The filters criteria are sent to the apps that are instrumented with the Application Insights SDK. The filter value could potentially contain sensitive information, such as the customer ID. To keep this value secured and prevent potential disclosure to unauthorized applications, you have two options:
 
-- **Recommended:** Secure the Live Metrics channel by using [Azure Active Directory (Azure AD) authentication](./azure-ad-authentication.md#configuring-and-enabling-azure-ad-based-authentication).
+- **Recommended:** Secure the Live Metrics channel by using [Azure Active Directory (Azure AD) authentication](./azure-ad-authentication.md#configure-and-enable-azure-ad-based-authentication).
 - **Legacy (no longer recommended):** Set up an authenticated channel by configuring a secret API key as explained in the "Legacy option" section.
 
 > [!NOTE]
diff --git a/articles/azure-monitor/app/tutorial-runtime-exceptions.md b/articles/azure-monitor/app/tutorial-runtime-exceptions.md
@@ -60,29 +60,28 @@ Application Insights collects any failures in your application. It lets you view
 
 1. The operations detail also shows a format exception, which appears to have caused the failure. You can see that it's because of an invalid Zip Code. You can open the debug snapshot to see code-level debug information in Visual Studio.
 
-	![Screenshot that shows Exception details.](media/tutorial-runtime-exceptions/failed-requests-exception.png)
+	![Screenshot that shows exception details.](media/tutorial-runtime-exceptions/failed-requests-exception.png)
 
 ## Identify failing code
 The Snapshot Debugger collects snapshots of the most frequent exceptions in your application to assist you in diagnosing its root cause in production. You can view debug snapshots in the portal to see the call stack and inspect variables at each call stack frame. Afterward, you can debug the source code by downloading the snapshot and opening it in Visual Studio 2019 Enterprise.
 
 1. In the properties of the exception, select **Open debug snapshot**.
-1. The **Debug Snapshot** pane opens with the call stack for the request. Select any method to view the values of all local variables at the time of the request. Starting from the top method in this example, we can see local variables that have no value.
+1. The **Debug Snapshot** pane opens with the call stack for the request. Select any method to view the values of all local variables at the time of the request. Starting from the top method in this example, you can see local variables that have no value.
 
-	![Screenshot that shows the debug snapshot.](media/tutorial-runtime-exceptions/debug-snapshot-01.png)
+	![Screenshot that shows the Debug Snapshot pane.](media/tutorial-runtime-exceptions/debug-snapshot-01.png)
 
-1. The first call that has valid values is **ValidZipCode**. We can see that a Zip Code was provided with letters that can't be translated into an integer. This issue appears to be the error in the code that must be corrected.
+1. The first call that has valid values is **ValidZipCode**. You can see that a Zip Code was provided with letters that can't be translated into an integer. This issue appears to be the error in the code that must be corrected.
 
 	![Screenshot that shows an error in the code that must be corrected.](media/tutorial-runtime-exceptions/debug-snapshot-02.png)
 
-1. You can then download this snapshot into Visual Studio where we can locate the actual code that must be corrected. To do so, select **Download Snapshot**.
+1. You can then download this snapshot into Visual Studio where you can locate the actual code that must be corrected. To do so, select **Download Snapshot**.
 1. The snapshot is loaded into Visual Studio.
 1. You can now run a debug session in Visual Studio Enterprise that quickly identifies the line of code that caused the exception.
 
-	![Screenshot that shows Exception in code.](media/tutorial-runtime-exceptions/exception-code.png)
-
+	![Screenshot that shows an exception in the code.](media/tutorial-runtime-exceptions/exception-code.png)
 
 ## Use analytics data
-All data collected by Application Insights is stored in Azure Log Analytics, which provides a rich query language that you can use to analyze the data in various ways. We can use this data to analyze the requests that generated the exception we're researching.
+All data collected by Application Insights is stored in Azure Log Analytics, which provides a rich query language that you can use to analyze the data in various ways. You can use this data to analyze the requests that generated the exception you're researching.
 
 1. Select the CodeLens information above the code to view telemetry provided by Application Insights.
 
@@ -92,17 +91,17 @@ All data collected by Application Insights is stored in Azure Log Analytics, whi
 
    ![Screenshot that shows Application Insights window that includes several queries.](media/tutorial-runtime-exceptions/analytics.png)<br>
 
-## Add work item
+## Add a work item
 If you connect Application Insights to a tracking system, such as Azure DevOps or GitHub, you can create a work item directly from Application Insights.
 
 1. Return to the **Exception Properties** pane in Application Insights.
 1. Select **New Work Item**.
 1. The **New Work Item** pane opens with details about the exception already populated. You can add more information before you save it.
 
-	![Screenshot that shows New Work Item.](media/tutorial-runtime-exceptions/new-work-item.png)
+	![Screenshot that shows the New Work Item pane.](media/tutorial-runtime-exceptions/new-work-item.png)
 
 ## Next steps
 Now that you've learned how to identify runtime exceptions, advance to the next tutorial to learn how to identify and diagnose performance issues.
 
 > [!div class="nextstepaction"]
-> * [Identify performance issues](./tutorial-performance.md)
+> [Identify performance issues](./tutorial-performance.md)
diff --git a/articles/azure-monitor/app/visual-studio.md b/articles/azure-monitor/app/visual-studio.md
@@ -25,7 +25,7 @@ In Visual Studio, you see a count of the events that were logged by the Applicat
 
 Select the **Application Insights** button to search your telemetry.
 
-## Application Insights search
+## Application Insights Search
 The **Application Insights Search** window shows logged events. If you signed in to Azure when you set up Application Insights, you can search the same events in the Azure portal. Right-click the project and select **Application Insights** > **Search**.
 
 ![Screenshot that shows the Application Insights Search window.](./media/visual-studio/34.png)
diff --git a/articles/azure-monitor/profiler/profiler.md b/articles/azure-monitor/profiler/profiler.md
@@ -97,7 +97,7 @@ To enable Azure AD for profiles ingestion:
 
    b.  [User-Assigned Managed identity documentation](../../app-service/overview-managed-identity.md?tabs=portal%2chttp#add-a-user-assigned-identity)
 
-1. [Configure and enable Azure AD](../app/azure-ad-authentication.md?tabs=net#configuring-and-enabling-azure-ad-based-authentication) in your Application Insights resource.
+1. [Configure and enable Azure AD](../app/azure-ad-authentication.md?tabs=net#configure-and-enable-azure-ad-based-authentication) in your Application Insights resource.
 
 1. Add the following application setting to let the Profiler agent know which managed identity to use:
 
diff --git a/articles/azure-monitor/snapshot-debugger/snapshot-debugger-app-service.md b/articles/azure-monitor/snapshot-debugger/snapshot-debugger-app-service.md
@@ -76,7 +76,7 @@ To turn-on Azure AD for snapshot ingestion:
 
     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 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. 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#configure-and-enable-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:
diff --git a/includes/application-insights-data-model-measurements.md b/includes/application-insights-data-model-measurements.md
@@ -5,10 +5,10 @@ ms.topic: include
 ms.date: 11/09/2018
 ms.author: mbullwin
 ---
-Collection of custom measurements. Use this collection to report named measurement associated with the telemetry item. Typical use cases are:
-- the size of Dependency Telemetry payload
-- the number of queue items processed by Request Telemetry
-- time that customer took to complete the step in wizard step completion Event Telemetry.
+Collection of custom measurements: Use this collection to report named measurements associated with the telemetry item. Typical use cases are:
+- The size of the Dependency telemetry payload.
+- The number of queue items processed by Request telemetry.
+- The time that a customer took to finish the wizard step completing Event telemetry.
 
 You can query custom measurements in Application Analytics:
 
@@ -19,6 +19,6 @@ customEvents
 ```
 
  > [!NOTE]
- > Custom measurements are associated with the telemetry item they belong to. They are subject to sampling with the telemetry item containing those measurements. To track a measurement that has a value independent from other telemetry types, use [Metric telemetry](../articles/azure-monitor/app/api-custom-events-metrics.md).
+ > Custom measurements are associated with the telemetry item they belong to. They're subject to sampling with the telemetry item that contains those measurements. To track a measurement that has a value independent from other telemetry types, use [Metric telemetry](../articles/azure-monitor/app/api-custom-events-metrics.md).
 
-Max key length: 150
+**Maximum key length**: 150
