Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into fixGrammer

Author: roygara

articles/aks/cluster-container-registry-integration.md

@@ -12,7 +12,7 @@ ms.devlang: azurecli
 
 You need to establish an authentication mechanism when using [Azure Container Registry (ACR)][acr-intro] with Azure Kubernetes Service (AKS). This operation is implemented as part of the Azure CLI, Azure PowerShell, and Azure portal experiences by granting the required permissions to your ACR. This article provides examples for configuring authentication between these Azure services.
 
-You can set up the AKS to ACR integration in a few steps using the Azure CLI, Azure PowerShell, or Azure portal. The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Azure Active Directory (Azure AD) **managed identity**][aad-identity] associated with your AKS cluster.
+You can set up the AKS to ACR integration using the Azure CLI or Azure PowerShell. The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Azure Active Directory (Azure AD) **managed identity**][aad-identity] associated with your AKS cluster.
 
 > [!NOTE]
 > This article covers automatic authentication between AKS and ACR. If you need to pull an image from a private external registry, use an [image pull secret][image-pull-secret].

articles/aks/use-mariner.md

@@ -5,7 +5,7 @@ description: Learn how to use the Mariner container host on Azure Kubernetes Ser
 services: container-service
 ms.topic: article
 ms.custom: ignite-2022
-ms.date: 09/22/2022
+ms.date: 11/17/2022
 ---
 
 # Use the Mariner container host on Azure Kubernetes Service (AKS)
@@ -52,7 +52,7 @@ Mariner currently has the following limitations:
 * Mariner does not yet have image SKUs for GPU, ARM64, SGX, or FIPS.
 * Mariner does not yet have FedRAMP, FIPS, or CIS certification.
 * Mariner cannot yet be deployed through Azure portal or Terraform.
-* Qualys and Trivy are the only vulnerability scanning tools that support Mariner today.
+* Qualys, Trivy, and Microsoft Defender for Containers are the only vulnerability scanning tools that support Mariner today.
 * The Mariner container host is a Gen 2 image. Mariner does not plan to offer a Gen 1 SKU.
 * Node configurations are not yet supported.
 * Mariner is not yet supported in GitHub actions.

articles/azure-monitor/app/app-map.md

@@ -400,7 +400,7 @@ Filters can be reused in two ways:
     later time may be different from the one observed when the link was
     created.
 
--   The dashboard pin :::image type="content" source="media/app-map/image-10.png" alt-text="A screenshot displaying the dashboard pin button."::: is located next to the title bar of the Application Map blade. This button pins the map to a dashboard, along with the filters applied to it. This action can be useful for filters that are frequently interesting. As an example, the user can pin a map with "Error connector" filter applied to it, and the dashboard view will only show nodes that have errors in their HTTP calls.
+-   The dashboard pin :::image type="content" source="media/app-map/image-10.png" alt-text="A screenshot displaying the dashboard pin button."::: is located next to the title bar of the Application Map pane. This button pins the map to a dashboard, along with the filters applied to it. This action can be useful for filters that are frequently interesting. As an example, the user can pin a map with "Error connector" filter applied to it, and the dashboard view will only show nodes that have errors in their HTTP calls.
 
 #### Filter usage scenarios
 

articles/azure-monitor/app/java-2x-collectd.md

@@ -88,7 +88,7 @@ Restart collectd according to its [manual](https://collectd.org/wiki/index.php/F
 ## View the data in Application Insights
 In your Application Insights resource, open [Metrics and add charts][metrics], selecting the metrics you want to see from the Custom category.
 
-By default, the metrics are aggregated across all host machines from which the metrics were collected. To view the metrics per host, in the Chart details blade, turn on Grouping and then choose to group by CollectD-Host.
+By default, the metrics are aggregated across all host machines from which the metrics were collected. To view the metrics per host, in the Chart details pane, turn on Grouping and then choose to group by CollectD-Host.
 
 ## To exclude upload of specific statistics
 By default, the Application Insights plugin sends all the data collected by all the enabled collectd 'read' plugins. 

articles/azure-monitor/app/java-2x-get-started.md

@@ -151,7 +151,7 @@ Either run it in debug mode on your development machine, or publish to your serv
 ## View your telemetry in Application Insights
 Return to your Application Insights resource in [Microsoft Azure portal](https://portal.azure.com).
 
-HTTP requests data appears on the overview blade. (If it isn't there, wait a few seconds and then click Refresh.)
+HTTP requests data appears on the overview pane. (If it isn't there, wait a few seconds and then click Refresh.)
 
 ![Screenshot of overview sample data](./media/java-get-started/overview-graphs.png)
 

articles/azure-monitor/app/java-2x-trace-logs.md

@@ -188,7 +188,7 @@ To start getting traces, merge the relevant snippet of code to the Log4J or Logb
 The Application Insights appenders can be referenced by any configured logger, and not necessarily by the root logger (as shown in the code samples above).
 
 ## Explore your traces in the Application Insights portal
-Now that you've configured your project to send traces to Application Insights, you can view and search these traces in the Application Insights portal, in the [Search][diagnostic] blade.
+Now that you've configured your project to send traces to Application Insights, you can view and search these traces in the Application Insights portal, in the [Search][diagnostic] pane.
 
 Exceptions submitted via loggers will be displayed on the portal as Exception Telemetry.
 

articles/azure-monitor/app/java-standalone-profiler.md

@@ -24,7 +24,7 @@ The Application Insights Java profiler uses the JFR profiler provided by the JVM
 
 This data is gathered on demand when trigger conditions are met. The available triggers are thresholds over CPU usage and Memory consumption.
 
-When a threshold is reached, a profile of the configured type and duration is gathered and uploaded. This profile is then visible within the performance blade of the associated Application Insights Portal UI.
+When a threshold is reached, a profile of the configured type and duration is gathered and uploaded. This profile is then visible within the performance pane of the associated Application Insights Portal UI.
 
 > [!WARNING]
 > The JFR profiler by default executes the "profile-without-env-data" profile. A JFR file is a series of events emitted by the JVM. The "profile-without-env-data" configuration, is similar to the "profile" configuration that ships with the JVM, however has had some events disabled that have the potential to contain sensitive deployment information such as environment variables, arguments provided to the JVM and processes running on the system.
@@ -93,8 +93,8 @@ The following steps will guide you through enabling the profiling component on t
 1. Configure the resource thresholds that will cause a profile to be collected:
 
     1. Browse to the Performance -> Profiler section of the Application Insights instance.
-       :::image type="content" source="./media/java-standalone-profiler/performance-blade.png" alt-text="Screenshot of the link to open performance blade." lightbox="media/java-standalone-profiler/performance-blade.png":::
-       :::image type="content" source="./media/java-standalone-profiler/profiler-button.png" alt-text="Screenshot of the Profiler button from the Performance blade." lightbox="media/java-standalone-profiler/profiler-button.png":::
+       :::image type="content" source="./media/java-standalone-profiler/performance-blade.png" alt-text="Screenshot of the link to open performance pane." lightbox="media/java-standalone-profiler/performance-blade.png":::
+       :::image type="content" source="./media/java-standalone-profiler/profiler-button.png" alt-text="Screenshot of the Profiler button from the Performance pane." lightbox="media/java-standalone-profiler/profiler-button.png":::
 
     2. Select "Triggers"
 

articles/azure-monitor/app/monitor-functions.md

@@ -29,7 +29,7 @@ The end-to-end diagnostics and the application map provide visibility into one s
 
 ### How to enable distributed tracing for Java Function apps
 
-Navigate to the functions app Overview blade and go to configurations. Under Application Settings, click "+ New application setting". 
+Navigate to the functions app Overview pane and go to configurations. Under Application Settings, click "+ New application setting". 
 
 > [!div class="mx-imgBorder"]
 > ![Under Settings, add new application settings](./media//functions/create-new-setting.png)

articles/azure-monitor/app/opentelemetry-enable.md

@@ -471,7 +471,7 @@ for i in range(100):
 ---
 
 > [!TIP]
-> If you're not sure where to set the sampling rate, start at 5% (i.e., 0.05 sampling ratio) and adjust the rate based on the accuracy of the operations shown in the failures and performance blades. A higher rate generally results in higher accuracy. However, ANY sampling will affect accuracy so we recommend alerting on [OpenTelemetry metrics](#metrics), which are unaffected by sampling.
+> If you're not sure where to set the sampling rate, start at 5% (i.e., 0.05 sampling ratio) and adjust the rate based on the accuracy of the operations shown in the failures and performance panes. A higher rate generally results in higher accuracy. However, ANY sampling will affect accuracy so we recommend alerting on [OpenTelemetry metrics](#metrics), which are unaffected by sampling.
 
 ## Instrumentation libraries
 

articles/azure-monitor/app/pre-aggregated-metrics-log-metrics.md

@@ -12,7 +12,7 @@ This article explains the difference between "traditional" Application Insights
 
 ## Log-based Metrics
 
-In the past, the application monitoring telemetry data model in Application Insights was solely based on a small number of predefined types of events, such as requests, exceptions, dependency calls, page views, etc. Developers can use the SDK to either emit these events manually (by writing code that explicitly invokes the SDK) or they can rely on the automatic collection of events from auto-instrumentation. In either case, the Application Insights backend stores all collected events as logs, and the Application Insights blades in the Azure portal act as an analytical and diagnostic tool for visualizing event-based data from logs.
+In the past, the application monitoring telemetry data model in Application Insights was solely based on a small number of predefined types of events, such as requests, exceptions, dependency calls, page views, etc. Developers can use the SDK to either emit these events manually (by writing code that explicitly invokes the SDK) or they can rely on the automatic collection of events from auto-instrumentation. In either case, the Application Insights backend stores all collected events as logs, and the Application Insights panes in the Azure portal act as an analytical and diagnostic tool for visualizing event-based data from logs.
 
 Using logs to retain a complete set of events can bring great analytical and diagnostic value. For example, you can get an exact count of requests to a particular URL with the number of distinct users who made these calls. Or you can get detailed diagnostic traces, including exceptions and dependency calls for any user session. Having this type of information can significantly improve visibility into the application health and usage, allowing to cut down the time necessary to diagnose issues with an app.