Merge pull request #277271 from alexbuckgit/alexbuckgit/docutune-autopr-20240605-130753-9016480-ignore-build

[BULK] - DocuTune - Minor formatting and syntax fixes (part 2)

Author: v-dirichards

articles/ai-services/language-service/sentiment-opinion-mining/how-to/use-containers.md

@@ -46,7 +46,7 @@ CPU core and memory correspond to the `--cpus` and `--memory` settings, which ar
 
 The Sentiment Analysis container image can be found on the `mcr.microsoft.com` container registry syndicate. It resides within the `azure-cognitive-services/textanalytics/` repository and is named `sentiment`. The fully qualified container image name is, `mcr.microsoft.com/azure-cognitive-services/textanalytics/sentiment`
 
-To use the latest version of the container, you can use the `latest` tag, which is for english. You can also find a full list of containers for supported languages using the [tags on the MCR](https://mcr.microsoft.com/product/azure-cognitive-services/textanalytics/sentiment/tags).
+To use the latest version of the container, you can use the `latest` tag, which is for English. You can also find a full list of containers for supported languages using the [tags on the MCR](https://mcr.microsoft.com/product/azure-cognitive-services/textanalytics/sentiment/tags).
 
 The sentiment analysis container v3 container is available in several languages. To download the container for the English container, use the command below. 
 
@@ -115,7 +115,7 @@ If you run the container with an output [mount](../../concepts/configure-contain
 
 ## Billing
 
-The Sentiment Analysis containers send billing information to Azure, using a _Language_ resource on your Azure account.
+The Sentiment Analysis containers send billing information to Azure, using a *Language* resource on your Azure account.
 
 [!INCLUDE [Container's Billing Settings](../../../includes/cognitive-services-containers-how-to-billing-info.md)]
 

articles/ai-studio/how-to/model-catalog-overview.md

@@ -45,6 +45,7 @@ Some models in the **Curated by Azure AI** and **Open models from the Hugging Fa
 ## Model deployment: Managed compute and serverless API (pay-as-you-go)  
 
 Model Catalog offers two distinct ways to deploy models from the catalog for your use: managed compute and serverless APIs. The deployment options available for each model vary; learn more about the features of the deployment options, and the options available for specific models, in the following tables. Learn more about [data processing]( concept-data-privacy.md) with the deployment options. 
+<!-- docutune:disable -->
 
 Features | Managed compute | serverless API (pay-as-you-go) 
 --|--|-- 
@@ -63,6 +64,7 @@ Phi3 family models | Phi-3-small-128k-Instruct <br> Phi-3-small-8k-Instruct <br>
 Nixtla | Not available | TimeGEN-1
 Other models | Available | Not available
 
+<!-- docutune:enable -->
 
 :::image type="content" source="../media/explore/platform-service-cycle.png" alt-text="A diagram showing models as a service and Real time end points service cycle." lightbox="../media/explore/platform-service-cycle.png":::
 
@@ -126,6 +128,8 @@ Azure AI Studio enables users to make use of Vector Indexes and Retrieval Augmen
 
 Pay-as-you-go billing is available only to users whose Azure subscription belongs to a billing account in a country where the model provider has made the offer available (see "offer availability region" in the table in the next section). If the offer is available in the relevant region, the user then must have a Hub/Project in the Azure region where the model is available for deployment or fine-tuning, as applicable (see "hub/project region" columns in the table below). 
 
+<!-- docutune:disable -->
+
 Model | Offer availability region  | Hub/Project Region for Deployment | Hub/Project Region for Fine-tuning
 --|--|--|--
 Llama-3-70B-Instruct <br> Llama-3-8B-Instruct | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) | East US 2, Sweden Central | Not available
@@ -134,6 +138,7 @@ Llama-2-7b-chat <br> Llama-2-13b-chat <br> Llama-2-70b-chat | [Microsoft Managed
 Mistral-Large <br> Mistral Small | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) | East US 2, Sweden Central | Not available
 Cohere-command-r-plus <br> Cohere-command-r <br> Cohere-embed-v3-english <br> Cohere-embed-v3-multilingual | [Microsoft Managed Countries](/partner-center/marketplace/tax-details-marketplace#microsoft-managed-countriesregions) <br> Japan | East US 2, Sweden Central | Not available
 
+<!-- docutune:enable -->
 
 ### Content safety for models deployed via Serverless API
 

articles/analysis-services/analysis-services-gateway.md

@@ -42,18 +42,18 @@ The following are fully qualified domain names used by the gateway.
 
 | Domain names | Outbound ports | Description |
 | --- | --- | --- |
-| *.powerbi.com |80 |HTTP used to download the installer. |
-| *.powerbi.com |443 |HTTPS |
-| *.analysis.windows.net |443 |HTTPS |
-| *.login.windows.net, login.live.com, aadcdn.msauth.net |443 |HTTPS |
-| *.servicebus.windows.net |5671-5672 |Advanced Message Queuing Protocol (AMQP) |
-| *.servicebus.windows.net |443, 9350-9354 |Listeners on Service Bus Relay over TCP (requires 443 for Access Control token acquisition) |
-| *.frontend.clouddatahub.net |443 |HTTPS |
-| *.core.windows.net |443 |HTTPS |
-| login.microsoftonline.com |443 |HTTPS |
-| *.msftncsi.com |443 |Used to test internet connectivity if the gateway is unreachable by the Power BI service. |
-| *.microsoftonline-p.com |443 |Used for authentication depending on configuration. |
-| dc.services.visualstudio.com    |443 |Used by AppInsights to collect telemetry. |
+| `*.powerbi.com` |80 |HTTP used to download the installer. |
+| `*.powerbi.com` |443 |HTTPS |
+| `*.analysis.windows.net` |443 |HTTPS |
+| `*.login.windows.net`, `login.live.com`, `aadcdn.msauth.net` |443 |HTTPS |
+| `*.servicebus.windows.net` |5671-5672 |Advanced Message Queuing Protocol (AMQP) |
+| `*.servicebus.windows.net` |443, 9350-9354 |Listeners on Service Bus Relay over TCP (requires 443 for Access Control token acquisition) |
+| `*.frontend.clouddatahub.net` |443 |HTTPS |
+| `*.core.windows.net` |443 |HTTPS |
+| `login.microsoftonline.com` |443 |HTTPS |
+| `*.msftncsi.com` |443 |Used to test internet connectivity if the gateway is unreachable by the Power BI service. |
+| `*.microsoftonline-p.com` |443 |Used for authentication depending on configuration. |
+| `dc.services.visualstudio.com`    |443 |Used by AppInsights to collect telemetry. |
 
 ## Next steps 
 

articles/app-service/deploy-local-git.md

@@ -153,15 +153,15 @@ When you push commits to your App Service repository, App Service deploys the fi
 
 You might see the following common error messages when you use Git to publish to an App Service app in Azure:
 
-|Message|Cause|Resolution
----|---|---|
+|Message|Cause|Resolution|
+|---|---|---|
 |`Unable to access '[siteURL]': Failed to connect to [scmAddress]`|The app isn't up and running.|Start the app in the Azure portal. Git deployment isn't available when the web app is stopped.|
 |`Couldn't resolve host 'hostname'`|The address information for the `azure` remote is incorrect.|Use the `git remote -v` command to list all remotes, along with the associated URL. Verify that the URL for the `azure` remote is correct. If needed, remove and recreate this remote using the correct URL.|
 |`No refs in common and none specified; doing nothing. Perhaps you should specify a branch such as 'main'.`|You didn't specify a branch during `git push`, or you haven't set the `push.default` value in `.gitconfig`.|Run `git push` again, specifying the main branch: `git push azure main`.|
 |`Error - Changes committed to remote repository but deployment to website failed.`|You pushed a local branch that doesn't match the app deployment branch on `azure`.|Verify that current branch is `master`. To change the default branch, use `DEPLOYMENT_BRANCH` application setting (see [Change deployment branch](#change-deployment-branch)). |
 |`src refspec [branchname] does not match any.`|You tried to push to a branch other than main on the `azure` remote.|Run `git push` again, specifying the main branch: `git push azure main`.|
 |`RPC failed; result=22, HTTP code = 5xx.`|This error can happen if you try to push a large git repository over HTTPS.|Change the git configuration on the local machine to make the `postBuffer` bigger. For example: `git config --global http.postBuffer 524288000`.|
-|`Error - Changes committed to remote repository but your web app not updated.`|You deployed a Node.js app with a _package.json_ file that specifies additional required modules.|Review the `npm ERR!` error messages before this error for more context on the failure. The following are the known causes of this error, and the corresponding `npm ERR!` messages:<br /><br />**Malformed package.json file**: `npm ERR! Couldn't read dependencies.`<br /><br />**Native module doesn't have a binary distribution for Windows**:<br />`npm ERR! \cmd "/c" "node-gyp rebuild"\ failed with 1` <br />or <br />`npm ERR! [modulename@version] preinstall: \make || gmake\ `|
+|`Error - Changes committed to remote repository but your web app not updated.`|You deployed a Node.js app with a _package.json_ file that specifies additional required modules.|Review the `npm ERR!` error messages before this error for more context on the failure. The following are the known causes of this error, and the corresponding `npm ERR!` messages:<br /><br />**Malformed package.json file**: `npm ERR! Couldn't read dependencies.`<br /><br />**Native module doesn't have a binary distribution for Windows**:<br />`npm ERR! \cmd "/c" "node-gyp rebuild"\ failed with 1` <br />or <br />`npm ERR! [modulename@version] preinstall: \make \|\| gmake\` |
 
 ## More resources