fix broken links

Author: lennessyy

docs/develop/go/nexus/feature-guide.mdx

@@ -552,7 +552,7 @@ See the [Nexus cancelation sample](https://github.com/temporalio/samples-go/tree
 
 ## Make Nexus calls across Namespaces in Temporal Cloud {#nexus-calls-across-namespaces-temporal-cloud}
 
-This section assumes you are already familiar with [how connect a Worker to Temporal Cloud](/develop/go/workers/cloud-worker).
+This section assumes you are already familiar with [how to connect a Worker to Temporal Cloud](/develop/go/client/temporal-client#connect-to-temporal-cloud).
 The same [source code](https://github.com/temporalio/samples-go/tree/main/nexus) is used in this section, but the `tcld` CLI will be used to create Namespaces and the Nexus Endpoint, and mTLS client certificates will be used to securely connect the caller and handler Workers to their respective Temporal Cloud Namespaces.
 
 ### Install the latest `tcld` CLI and generate certificates

docs/develop/python/workers/serverless-workers/aws-lambda.mdx

@@ -64,7 +64,7 @@ lambda_handler = run_worker(
 <!--SNIPEND-->
 
 `run_worker` takes a `WorkerDeploymentVersion` and a configure callback, and returns a Lambda handler.
-The `WorkerDeploymentVersion` identifies the [Worker Deployment](/worker-versioning#deployments) and [Build Id](/worker-versioning#build-id) for this Worker.
+The `WorkerDeploymentVersion` identifies the [Worker Deployment](/worker-versioning#deployments) and [Build ID](/worker-versioning#deployment-versions) for this Worker.
 The deployment name groups related Workers across versions, and the Build Id identifies a specific release of your Worker code.
 Worker Versioning is required for Serverless Workers.
 

docs/encyclopedia/workers/worker-versioning.mdx

@@ -34,7 +34,7 @@ Each Deployment has a name (such as your service name) and supports versioning t
 ## Worker Deployment Versions {#deployment-versions}
 
 A Worker Deployment Version represents an iteration of a Worker Deployment.
-Each Deployment Version is identified by a deployment name and a <span id="build-id">Build ID</span>.
+Each Deployment Version is identified by a deployment name and a Build ID.
 The deployment name groups related Workers across versions, and the Build ID identifies a specific release of your Worker code.
 Each Deployment Version consists of Workers that share the same code build and environment.
 When a Worker starts polling for Workflow and Activity Tasks, it reports its Deployment Version to the Temporal Server.

docs/troubleshooting/serverless-workers.mdx

@@ -35,9 +35,9 @@ This page walks through the Serverless Worker invocation flow and helps you iden
 When a Serverless Worker invocation works correctly, the following sequence happens:
 
 1. You deploy the Worker function on Lambda.
-2. You configure a [Worker Deployment Version](/worker-versioning#worker-deployment-version) with a compute provider. This starts a [Worker Controller Instance (WCI)](/serverless-workers#how-invocation-works) Workflow and a validation invocation of the Lambda function.
-3. The Lambda polls the Temporal Service successfully, binding the [Task Queue](/encyclopedia/task-queues) configured on the Worker to the Worker Deployment Version.
-4. The WCI continuously monitors the associated Task Queue on a schedule. The [Matching Service](/clusters#matching-service) also notifies the WCI Workflow of sync match failures immediately as they happen.
+2. You configure a [Worker Deployment Version](/worker-versioning#deployment-versions) with a compute provider. This starts a [Worker Controller Instance (WCI)](/serverless-workers#how-invocation-works) Workflow and a validation invocation of the Lambda function.
+3. The Lambda polls the Temporal Service successfully, binding the [Task Queue](/task-queue) configured on the Worker to the Worker Deployment Version.
+4. The WCI continuously monitors the associated Task Queue on a schedule. The [Matching Service](/temporal-service/temporal-server#matching-service) also notifies the WCI Workflow of sync match failures immediately as they happen.
 5. A Task arrives on the Task Queue and the WCI detects the backlog.
 6. The WCI invokes the Lambda function.
 7. The Lambda function starts, the Worker connects to Temporal and polls the Task Queue.
@@ -71,7 +71,7 @@ role, and that the Lambda function can be invoked.
 
 If validation fails, verify that the Lambda function ARN and invocation role ARN in the Worker Deployment Version
 configuration are correct. Verify the invocation role was created using the
-[CloudFormation template](/production-deployment/worker-deployments/serverless-workers/aws-lambda#create-invocation-role)
+[CloudFormation template](/production-deployment/worker-deployments/serverless-workers/aws-lambda#configure-iam)
 and that the External ID matches the value in the Worker Deployment Version configuration.
 
 If the Worker Deployment Version does not have a compute provider configured, no
@@ -134,7 +134,7 @@ Common errors include:
 - **Connection failures**: The Worker cannot reach the Temporal Service. Check that the `TEMPORAL_ADDRESS` and
   `TEMPORAL_API_KEY` environment variables (or `temporal.toml` config file) are correctly set on the Lambda function.
   For self-hosted deployments, verify
-  [network reachability](/production-deployment/worker-deployments/serverless-workers/self-hosted-setup#ensure-reachability).
+  [network reachability](/production-deployment/worker-deployments/serverless-workers/self-hosted-setup#ensure-network-reachability).
 - **TLS errors**: The TLS certificate or key is missing, expired, or does not match the Namespace.
 - **Authentication errors**: The API key is invalid or does not have access to the Namespace.
 

docusaurus.config.js

@@ -9,8 +9,8 @@ module.exports = async function createConfigAsync() {
     tagline: 'Build invincible applications',
     url: 'https://docs.temporal.io',
     baseUrl: '/',
-    onBrokenLinks: 'warn',
-    onBrokenAnchors: 'warn',
+    onBrokenLinks: 'throw',
+    onBrokenAnchors: 'throw',
     favicon: 'img/favicon.ico',
     organizationName: 'temporalio', // Usually your GitHub org/user name.
     projectName: 'temporal-documentation', // Usually your repo name.