Merge pull request #6790 from aahill/ptu-spillover

fixes

Author: prmerger-automator[bot]

articles/ai-foundry/agents/concepts/model-region-support.md

@@ -26,7 +26,7 @@ Azure AI Foundry Agent Service supports the following Azure OpenAI models in the
 
 > [!NOTE]
 > * [Hub-based projects](../../what-is-azure-ai-foundry.md#project-types) are limited to the following models: gpt-4o, gpt-4o-mini, gpt-4, gpt-35-turbo
-> * The [spillover feature](../../openai/how-to/spillover-traffic-management.md) for provisioned throughput is compatable with agents
+> * [Spillover traffic management](../../openai/how-to/spillover-traffic-management.md) for [provisioned throughput](../../openai/concepts/provisioned-throughput.md) is compatible with agents
 > * For information on class A subnet support, see the setup guide on [GitHub](https://github.com/azure-ai-foundry/foundry-samples/tree/main/samples/microsoft/infrastructure-setup/15-private-network-standard-agent-setup).
 > * The [file search tool](../how-to/tools/file-search.md) is currently unavailable in the following regions:
 >     * Italy north

articles/ai-foundry/openai/how-to/spillover-traffic-management.md

@@ -102,7 +102,7 @@ The following Azure Monitor metrics chart provides an example of the split of re
     The following example shows an instance where a spike in requests sent to the provisioned throughput deployment generates `429` error codes. Shortly after, spillover occurs and requests begin to be sent to the pay-as-you-go deployment being used for spillover, generating `200` responses for that deployment.
 
 
-    :::image type="content" source="../media/provisioned/spillover-chart-simplified.png" alt-text="A screenshot showing the metrics for a basic spillover example in the Azure portal." lightbox="../media/provisioned/spillover-chart-simplified.png":::
+    :::image type="content" source="../media/provisioned/spillover-chart-simplified.png" alt-text="A screenshot showing the metrics for visualizing spillover." lightbox="../media/provisioned/spillover-chart-simplified.png":::
 
     > [!NOTE]
     > As requests are sent to the pay-as-you-go deployment, they still will generate 429 response codes on the provisioned deployment before being redirected.