[AIG, Ref Arch] Hyperlint Automation: Broken Link Fixes (#19878)

---------

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: Pedro Sousa <[email protected]>

Author: 2 people

src/content/docs/ai-gateway/index.mdx

@@ -37,7 +37,7 @@ View metrics such as the number of requests, tokens, and the cost it takes to ru
 
 </Feature>
 
-<Feature header="Logging" href="/ai-gateway/observability/analytics/#logging" cta="View Logging">
+<Feature header="Logging" href="/ai-gateway/observability/logging/" cta="View Logging">
 
 Gain insight on requests and errors.
 

src/content/docs/reference-architecture/diagrams/ai/ai-multivendor-observability-control.mdx

@@ -38,7 +38,7 @@ The following architecture illustrates the setup of [AI Gateway](/ai-gateway/) a
 ![Figure 1: Multi-vendor AI architecture](~/assets/images/reference-architecture/ai-multivendor-observability-control/ai-multi-vendor-observability-control.svg "Multi-vendor AI architecture")
 
 1. **Inference request**: Send POST request to your AI gateway.
-2. **Request proxying**: Forward `POST` request to AI Inference provider or serve response from [cache, if enabled and available](/ai-gateway/configuration/caching). During this process, both [analytics](/ai-gateway/observability/analytics/) and [logs](/ai-gateway/observability/analytics/#logging) are collected. Additionally, controls such as Rate Limiting are enforced.
+2. **Request proxying**: Forward `POST` request to AI Inference provider or serve response from [cache, if enabled and available](/ai-gateway/configuration/caching). During this process, both [analytics](/ai-gateway/observability/analytics/) and [logs](/ai-gateway/observability/logging/) are collected. Additionally, controls such as Rate Limiting are enforced.
 3. **Error handling**: In case of errors, retry request or fallback to other inference provider, depending on configuration.
 
 ## Related resources

src/content/docs/reference-architecture/diagrams/ai/ai-video-caption.mdx

@@ -29,7 +29,7 @@ The process begins with capturing the audio from the video source, which is then
 ![Figure 1: Automatic captioning on upload](~/assets/images/reference-architecture/ai-auto-caption-architecture-diagrams/ai-auto-caption-architecture-diagram.svg "Figure 1:  Automatic captioning on upload")
 
 1. **Client upload**: Send POST request with both video and audio to API endpoint.
-2. **Audio transcription**: Generate timestamped transcriptions by calling [Workers AI](/workers-ai/) [automatic speech recognition (ARS) model](/workers-ai/models/#automatic-speech-recognition) with audio as input. Use [Workers](/workers/) to convert the output to a supported subtitled format.
+2. **Audio transcription**: Generate timestamped transcriptions by calling [Workers AI](/workers-ai/) [automatic speech recognition (ARS) model](/workers-ai/models/) with audio as input. Use [Workers](/workers/) to convert the output to a supported subtitled format.
 3. **Store subtitles**: Store the subtitle file(s) on [R2](/r2/).
 4. **Store video**: Store the video files on [R2](/r2/).
 5. **Client request**: Send GET requests for video and subtitle(s) to origin. Use global [Cache](/cache/) to increase performance.
@@ -38,5 +38,5 @@ The process begins with capturing the audio from the video source, which is then
 ## Related resources
 
 - [Community project: automatic captioning demo](https://auto-caption.pages.dev/)
-- [Workers AI: Automatic speech recognition (ARS) model](/workers-ai/models/#automatic-speech-recognition)
+- [Workers AI: Automatic speech recognition (ARS) model](/workers-ai/models/)
 - [R2: Object storage for all your data](/r2/)