Merge pull request #268204 from MicrosoftDocs/main

3/6 11:00 AM IST Publish

Author: Saisang

articles/ai-services/containers/azure-kubernetes-recipe.md

@@ -191,7 +191,7 @@ The following steps are needed to get the required information to connect your c
 1. Get your container registry ID.
 
     ```azurecli-interactive
-    az acr show --resource-group cogserv-container-rg --name pattyregistry --query "id" --o table
+    az acr show --resource-group cogserv-container-rg --name pattyregistry --query "id" --output table
     ```
 
     Save the output for the scope parameter value, `<acrId>`, in the next step. It looks like:

articles/ai-services/language-service/text-analytics-for-health/how-to/use-containers.md

@@ -70,7 +70,7 @@ Once the container is on the host computer, use the [docker run](https://docs.do
 There are multiple ways you can install and run the Text Analytics for health container. 
 
 - Use the Azure portal to create a Language resource, and use Docker to get your container.
-- Use an Azure VM with Docker to run the container. Refer to [Docker on Azure](../../../../docker/index.yml).
+- Use an Azure VM with Docker to run the container. 
 - Use the following PowerShell and Azure CLI scripts to automate resource deployment and container configuration.
 
 When you use the Text Analytics for health container, the data contained in your API requests and responses is not visible to Microsoft, and is not used for training the model applied to your data. 

articles/ai-services/openai/whisper-quickstart.md

@@ -94,7 +94,7 @@ echo export AZURE_OPENAI_ENDPOINT="REPLACE_WITH_YOUR_ENDPOINT_HERE" >> /etc/envi
 
 ::: zone pivot="programming-language-python"
 
-[!INCLUDE [REST API quickstart](includes/whisper-python.md)]
+[!INCLUDE [Python quickstart](includes/whisper-python.md)]
 
 ::: zone-end
 

articles/ai-studio/how-to/generate-data-qa.md

@@ -27,9 +27,9 @@ pip3 install azure-identity azure-ai-generative
 pip3 install wikipedia langchain nltk unstructured
 ```
 
-## Connect to Azure Open AI
+## Connect to Azure OpenAI
 
-We need to connect to Azure Open AI so that we can access the LLM to generate data for us.
+We need to connect to Azure OpenAI so that we can access the LLM to generate data for us.
 
 ```python
 from azure.ai.resources.client import AIClient 
@@ -175,7 +175,7 @@ To use the `generated_qa.jsonl` file for evaluation, you need to add this file a
 
 ## Generate data from files
 
-Generating data from files might be more practical for large amounts of data. You can use the `generate_async()` function OF THE `QADataGenerator` to make concurrent requests to Azure Open AI for generating data from files.
+Generating data from files might be more practical for large amounts of data. You can use the `generate_async()` function OF THE `QADataGenerator` to make concurrent requests to Azure OpenAI for generating data from files.
 
 Files might have large texts that go beyond model's context lengths. They need to be split to create smaller chunks. Moreover, they shouldn't be split mid-sentence. Such partial sentences might lead to improper QA samples. You can use LangChain's `NLTKTextSplitter` to split the files before generating data.
 

articles/application-gateway/for-containers/how-to-header-rewrite-ingress-api.md

@@ -6,7 +6,7 @@ author: greg-lindsay
 ms.service: application-gateway
 ms.subservice: appgw-for-containers
 ms.topic: conceptual
-ms.date: 02/27/2024
+ms.date: 03/5/2024
 ms.author: greglin
 ---
 
@@ -43,7 +43,7 @@ The following figure illustrates an example of a request with a specific user ag
    - two services called `backend-v1` and `backend-v2` in the `test-infra` namespace
    - two deployments called `backend-v1` and `backend-v2` in the `test-infra` namespace
 
-## Deploy the required Gateway API resources
+## Deploy the required Ingress API resources
 
 # [ALB managed deployment](#tab/alb-managed)
 
@@ -200,7 +200,7 @@ spec:
 EOF
 ```
 
-Once the HTTPRoute resource is created, ensure the route has been _Accepted_ and the Application Gateway for Containers resource has been _Programmed_.
+Once the IngressExtension resource is created, ensure the resource returns _No validation errors_ and is valid.
 
 ```bash
 kubectl get IngressExtension header-rewrite -n test-infra -o yaml
@@ -333,4 +333,4 @@ Via the response we should see:
 }
 ```
 
-Congratulations, you have installed ALB Controller, deployed a backend application and modified header values via Gateway API on Application Gateway for Containers.
+Congratulations, you have installed ALB Controller, deployed a backend application and modified header values via Ingress API on Application Gateway for Containers.

articles/azure-maps/android-sdk-migration-guide.md

@@ -22,7 +22,7 @@ To use the Map Control in a web page, you must have one of the following prerequ
 
 ## Create a WebView
 
-Add a `WebView` if your Android application doesn't have one. Do so by adding the `WebView` element to your layout XML or programmatically in your Java code. Be sure it's configured to occupy the desired area of your layout.
+Add a WebView if your Android application doesn't have one. Do so by adding the `WebView` element to your layout XML or programmatically in your Java code. Be sure it's configured to occupy the desired area of your layout.
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
@@ -41,13 +41,13 @@ Add a `WebView` if your Android application doesn't have one. Do so by adding th
 </androidx.coordinatorlayout.widget.CoordinatorLayout>
 ```
 
-Enable internet access by adding permissions in AndroidManifest.xml.
+Enable internet access by adding permissions in _AndroidManifest.xml_.
 
 ```xml
 <uses-permission android:name="android.permission.INTERNET" />
 ```
 
-In your activity or fragment, initialize the WebView and enable JavaScript by updating the settings. Load the HTML file that contains the Web SDK code. You can either load it from the assets folder or from a remote URL.
+In your activity or fragment, initialize the `WebView` and enable JavaScript by updating the settings. Load the HTML file that contains the Web SDK code. You can either load it from the assets folder or from a remote URL.
 
 ```java
 import android.os.Bundle;
@@ -134,13 +134,13 @@ In your HTML file, initialize a map with your subscription key. Replace `<YOUR_S
 </html>
 ```
 
-Save and run the app. A map should be shown within a WebView. Add any features or functionalities that you want to use from the Web SDK. You can refer to the [Azure Maps documentation] and the [Azure Maps Code Samples website] for more use cases.
+Save and run the app. A map will appear within a WebView. Add any required features or functionality from the Web SDK. For more information, see [Azure Maps Documentation] and [Azure Maps Samples].
 
 :::image type="content" source="./media/android-sdk-migration-guide/maps-android.png" alt-text="A screenshot of a map in a WebView.":::
 
 ## Communication between native code and WebView (optional)
 
-To enable communication between your Android application and the WebView, you can use the WebView's `addJavascriptInterface` method to expose a Java object to the JavaScript running in the WebView. It allows you to call Java methods from your JavaScript code. For more information, see the [Android WebView documentation].
+To enable communication between your Android application and the WebView, you can use the WebView's `addJavascriptInterface` method to expose a Java object to the JavaScript running in the WebView. It allows you to call Java methods from your JavaScript code. For more information, see [WebView] in the Android documentation.
 
 ## Clean Up Native Map Implementation
 
@@ -160,9 +160,7 @@ Learn how to add maps to web and mobile applications using the Map Control clien
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
 [authentication options]: /javascript/api/azure-maps-control/atlas.authenticationoptions
-[Azure Maps documentation]: how-to-use-map-control.md
-[Azure Maps Code Samples website]: https://samples.azuremaps.com/
-[Android WebView documentation]: https://developer.android.com/reference/android/webkit/WebView
+[Azure Maps Documentation]: how-to-use-map-control.md
+[Azure Maps Samples]: https://samples.azuremaps.com/
+[WebView]: https://developer.android.com/reference/android/webkit/WebView
 [Use the Azure Maps map control]: how-to-use-map-control.md
-
-

articles/azure-maps/ios-sdk-migration-guide.md

@@ -22,7 +22,7 @@ To use the Map Control in a web page, you must have one of the following prerequ
 
 ## Create a WebView
 
-Add a `WebView` if your iOS application doesn't have one. Do so by adding the `WKWebView` to your storyboard or programmatically in your Swift code. Be sure it's configured to occupy the desired area of your layout.
+Add a WebView if your iOS application doesn't have one. Do so by adding the `WKWebView` to your storyboard or programmatically in your Swift code. Be sure it's configured to occupy the desired area of your layout.
 
 ```swift
 import UIKit
@@ -117,7 +117,7 @@ In your HTML file, initialize a map with your subscription key. Replace `<YOUR_S
 </html>
 ```
 
-Save and run the app. A map should be shown within a WebView. Add any features or functionalities that you want to use from the Web SDK. You can refer to the [Azure Maps documentation] and the [Azure Maps Code Samples website] for more use cases.
+Save and run the app. A map should be shown within a WebView. Add any features or functionalities that you want to use from the Web SDK. You can refer to the [Azure Maps Documentation] and the [Azure Maps Samples] for more use cases.
 
 :::image type="content" source="./media/ios-sdk-migration-guide/maps-ios.png" alt-text="A screenshot of a map in a WebView.":::
 
@@ -143,8 +143,8 @@ Learn how to add maps to web and mobile applications using the Map Control clien
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
 [authentication options]: /javascript/api/azure-maps-control/atlas.authenticationoptions
-[Azure Maps documentation]: how-to-use-map-control.md
-[Azure Maps Code Samples website]: https://samples.azuremaps.com/
+[Azure Maps Documentation]: how-to-use-map-control.md
+[Azure Maps Samples]: https://samples.azuremaps.com/
 [WKScriptMessageHandler]: https://developer.apple.com/documentation/webkit/wkscriptmessagehandler
 [Use the Azure Maps map control]: how-to-use-map-control.md
 

articles/azure-monitor/agents/om-agents.md

@@ -220,8 +220,6 @@ union *
 
 When you no longer require integration between your Operations Manager management group and the Log Analytics workspace, several steps are required to properly remove the connection and configuration in the management group. The following procedure has you update your Log Analytics workspace by deleting the reference of your management group, deleting the Azure Monitor connectors, and then deleting management packs that support integration with the service.
 
-Management packs for the solutions you've enabled that integrate with Operations Manager and the management packs required to support integration with Azure Monitor can't be easily deleted from the management group. The reason is that some of the Azure Monitor management packs have dependencies on other related management packs. To delete management packs that have a dependency on other management packs, download the script to [remove a management pack with dependencies](https://gallery.technet.microsoft.com/scriptcenter/Script-to-remove-a-84f6873e) from TechNet Script Center.
-
 1. Open the Operations Manager command shell with an account that's a member of the Operations Manager Administrators role.
 
     > [!WARNING]

articles/azure-monitor/containers/monitor-kubernetes.md

@@ -121,7 +121,7 @@ If you have an existing Grafana environment, then you can continue to use it and
 
 When you enable Container Insights for your Kubernetes cluster, it deploys a containerized version of the [Azure Monitor agent](../agents/log-analytics-agent.md) that sends data to a Log Analytics workspace in Azure Monitor. Container insights collects container stdout/stderr, infrastructure logs, and performance data. All log data is stored in a Log Analytics workspace where they can be analyzed using [Kusto Query Language (KQL)](../logs/log-query-overview.md).
 
-See [Enable Container insights](../containers/container-insights-onboard.md) for prerequisites and configuration options for onboarding your Kubernetes clusters. [Onboard using Azure Policy](container-insights-enable-aks-policy.md) to ensure that all clusters retain a consistent configuration. 
+See [Enable Container insights](../containers/container-insights-onboard.md) for prerequisites and configuration options for onboarding your Kubernetes clusters. [Onboard using Azure Policy](/azure/azure-monitor/containers/kubernetes-monitoring-enable?tabs=policy#enable-container-insights) to ensure that all clusters retain a consistent configuration. 
 
 Once Container insights is enabled for a cluster, perform the following actions to optimize your installation.
 

articles/azure-netapp-files/understand-path-lengths.md

@@ -11,7 +11,7 @@ ms.author: anfdocs
 
 # Understand path lengths in Azure NetApp Files 
 
-File and path length refers to the number of Unicode characters in a file path, including directories. This limit is a factor if the individual character lengths, which are determined by the size of the character in bytes. For instance, NFS and SMB allow path components of 255 bytes. The file encoding format of ASCII uses 8-bit encoding, meaning file path components (such as a file or folder name) in ASCII can be up to 255 characters since ASCII characters are 1 byte in size. 
+File and path length refers to the number of Unicode characters in a file path, including directories. This limit is a factor in the individual character lengths, which are determined by the size of the character in bytes. For instance, NFS and SMB allow path components of 255 bytes. The file encoding format of ASCII uses 8-bit encoding, meaning file path components (such as a file or folder name) in ASCII can be up to 255 characters since ASCII characters are 1 byte in size. 
 
 The following table shows the supported component and path lengths in Azure NetApp Files volumes: