changes

Author: ssalgadodev

articles/ai-foundry/how-to/configure-managed-network.md

@@ -29,7 +29,7 @@ You need to configure following network isolation configurations.
 - Choose network isolation mode. You have two options: allow internet outbound mode or allow only approved outbound mode.
 - If you use Visual Studio Code integration with allow only approved outbound mode, create FQDN outbound rules described in the [use Visual Studio Code](#scenario-use-visual-studio-code) section.
 - If you use HuggingFace models in Models with allow only approved outbound mode, create FQDN outbound rules described in the [use HuggingFace models](#scenario-use-huggingface-models) section.
-- If you use one of the open-source models with allow only approved outbound mode, create FQDN outbound rules described in the [Models Sold Directly by Azure ](#scenario-azure-direct-models) section.
+- If you use one of the open-source models with allow only approved outbound mode, create FQDN outbound rules described in the [Models Sold Directly by Azure](#scenario-models-sold-directly-by-azure) section.
 
 ## Network isolation architecture and isolation modes
 

articles/ai-foundry/model-inference/concepts/models.md

@@ -17,7 +17,7 @@ ms.custom: references_regions, tool_generated
 
 Azure AI Foundry Models gives you access to flagship models in Azure AI Foundry to consume them as APIs without hosting them on your infrastructure.
 
-A selection of models is offered directly by Microsoft under [Models Sold Directly by Azure](#azure-direct-models) which brings the most powerful options to developers to build AI applications. We also enable the breath of models by partnering with key players in the industry and bringing [Models from Partners and Community](#models-from-partners-and-community).
+A selection of models is offered directly by Microsoft under [Models Sold Directly by Azure](#models-sold-directly-by-azure) which brings the most powerful options to developers to build AI applications. We also enable the breath of models by partnering with key players in the industry and bringing [Models from Partners and Community](#models-from-partners-and-community).
 
 
 :::image type="content" source="../media/models/models-catalog.gif" alt-text="An animation showing Azure AI Foundry portal model catalog section and the models available." lightbox="../media/models/models-catalog.gif":::

articles/ai-foundry/model-inference/how-to/manage-costs.md

@@ -46,7 +46,7 @@ To understand the breakdown of what makes up the cost, it can be helpful to use
 5. By default, cost analysis is scoped to the selected resource group.
 
     > [!IMPORTANT]
-    > It's important to scope *Cost Analysis* to the resource group where the Azure AI Foundry resource is deployed. Cost meters associated with [Models from Partners and Community](#models-from-paterners-and-community) are displayed under the resource group instead of the Azure AI Foundry resource.
+    > It's important to scope *Cost Analysis* to the resource group where the Azure AI Foundry resource is deployed. Cost meters associated with [Models from Partners and Community](#models-from-partners-and-community) are displayed under the resource group instead of the Azure AI Foundry resource.
 
 6. Modify **Group by** to **Meter**. You can now see that for this particular resource group, the source of the costs comes from different models series.  
 
@@ -56,7 +56,7 @@ The following sections explain the entries in details.
 
 ### Models Sold Directly by Azure 
 
-[Models Sold Directly by Azure](../concepts/models.md#azure-direct-models) (including Azure OpenAI) are charged directly and they show up as billing meters under each Azure AI Foundry resource (formerly known Azure AI Services). This billing happens directly through Microsoft. When you inspect your bill, you notice billing meters accounting for inputs and outputs for each consumed model.
+[Models Sold Directly by Azure](../concepts/models.md#models-sold-directly-by-azure) (including Azure OpenAI) are charged directly and they show up as billing meters under each Azure AI Foundry resource (formerly known Azure AI Services). This billing happens directly through Microsoft. When you inspect your bill, you notice billing meters accounting for inputs and outputs for each consumed model.
 
 :::image type="content" source="../media/manage-cost/cost-by-meter-1p.png" alt-text="Screenshot of cost analysis dashboard scoped to the resource group where the Azure AI Foundry resource is deployed, highlighting the meters for Azure OpenAI and Phi models. Cost is group by meter." lightbox="../media/manage-cost/cost-by-meter-1p.png":::
 
@@ -67,7 +67,7 @@ Models provided by third-party providers, like Cohere, are billed using Azure Ma
 :::image type="content" source="../media/manage-cost/cost-by-meter-saas.png" alt-text="Screenshot of cost analysis dashboard scoped to the resource group where the Azure AI Foundry resource is deployed, highlighting the meters for models billed throughout Azure Marketplace. Cost is group by meter." lightbox="../media/manage-cost/cost-by-meter-saas.png":::
 
 > [!IMPORTANT]
-> This distinction between [Models Sold Directly by Azure ](../concepts/models.md#azure-direct-models) (including Azure OpenAI) and [Models from Partners and Community](../concepts/models.md#models-from-paterners-and-community) only affects how the model is made available to you and how you are charged. In all cases, models are hosted within Azure cloud and there is no interaction with external services or providers.
+> This distinction between [Models Sold Directly by Azure ](../concepts/models.md#models-sold-directly-by-azure) (including Azure OpenAI) and [Models from Partners and Community](../concepts/models.md#models-from-partners-and-community) only affects how the model is made available to you and how you are charged. In all cases, models are hosted within Azure cloud and there is no interaction with external services or providers.
 
 ### Using Azure Prepayment
 

articles/ai-foundry/model-inference/includes/create-model-deployments/intro.md

@@ -19,4 +19,4 @@ To complete this article, you need:
 
 * An Azure AI Foundry resource (formerly known as Azure AI Services). For more information, see [Create and configure all the resources for Azure AI Foundry Models](../../how-to/quickstart-create-resources.md).
 
-* [Models from Partners and Community](../../concepts/models.md#models-from-partners-and-community) require access to **Azure Marketplace**. Ensure you have the [permissions required to subscribe to model offerings](../../how-to/configure-marketplace.md). [Models Sold Directly by Azure](../../concepts/models.md#azure-direct-models) don't have this requirement.
+* [Models from Partners and Community](../../concepts/models.md#models-from-partners-and-community) require access to **Azure Marketplace**. Ensure you have the [permissions required to subscribe to model offerings](../../how-to/configure-marketplace.md). [Models Sold Directly by Azure](../../concepts/models.md#models-sold-directly-by-azure) don't have this requirement.

articles/machine-learning/how-to-network-isolation-model-catalog.md

@@ -45,7 +45,7 @@ Since the workspace managed virtual network can access internet in this configur
 1. Configure a workspace by following [Workspace managed network isolation](./how-to-managed-network.md#configure-a-managed-virtual-network-to-allow-only-approved-outbound). In step 3 of the tutorial when selecting **Workspace managed outbound access**, select **Allow Only Approved Outbound**.  
 2. If you set the public network access to the workspace to disabled, you can connect to the workspace using one of the methods as listed [in step 2 of the allow internet outbound section of this tutorial](#workspace-managed-virtual-network-to-allow-internet-outbound).
 3. The workspace manages virtual network is set to an allow only configuration. You must add a corresponding user-defined outbound rule to allow all the relevant FQDNs.
-    1. Follow this link for a list of FQDNs required for the [Models Sold Directly by Azure collection](#language-models-in-azure-direct-models-collection).
+    1. Follow this link for a list of FQDNs required for the [Models Sold Directly by Azure collection](#language-models-in-models-sold-directly-by-azure-collection).
     2. Follow this link for a list of FQDNs required for the [Hugging Face collection](#work-with-hugging-face-collection). 
 
 ## Work with open source models curated by Azure Machine Learning