Merge pull request #73 from depot/seo-fixes

Update with audit fixes

content/container-builds/overview.mdx

@@ -16,7 +16,7 @@ That's it! You can now build your Docker images up to 40x faster than building t
 
 Best of all, Depot's build infrastructure for container builds requires zero configuration on your part; everything just works, including the build cache!
 
-Take a look at the [quickstart](/docs/quickstart) to get started.
+Take a look at the [quickstart](/docs/container-builds/quickstart) to get started.
 
 ## How does it work?
 
@@ -78,7 +78,7 @@ The flow of a given Docker image build when using Depot looks like this:
 5. After the `machine-agent` reports that BuildKit is running, the Depot API returns a successful response to the Depot CLI, along with new mTLS certificates to secure and authenticate the build connection
 6. The Depot CLI uses the new mTLS certificates to directly connect to the builder instance, using that machine and cache volume for the build
 
-The same architecture is used for [self-hosted builders](/docs/self-hosted/architecture), the only difference being where the `cloud-agent` and builder virtual machines launch.
+The same architecture is used for [self-hosted builders](/docs/managed/overview), the only difference being where the `cloud-agent` and builder virtual machines launch.
 
 ## Common opportunities to use Depot remote container builds
 

content/guides/devcontainers.mdx

@@ -12,7 +12,7 @@ With Depot, you can build your Dev Containers on demand with instant shared cach
 
 ## How to use Depot with Dev Containers
 
-First, you will need to make sure you have [installed the `depot` CLI](/docs/quickstart#installing-the-cli) and [configured a project](/docs/quickstart#creating-a-project).
+First, you will need to make sure you have [installed the `depot` CLI](/docs/container-builds/quickstart#installing-the-cli) and [configured a project](/docs/container-builds/quickstart#creating-a-project).
 
 ### Connect to your Depot project from the `depot` CLI
 

content/guides/local-development.mdx

@@ -14,7 +14,7 @@ There is nothing additional you need to configure to share your build cache acro
 
 ## How to use Depot for local development
 
-To leverage Depot locally, [install the `depot` CLI tool](/docs/cli/installation) and [configure your Depot project](https://depot.dev/docs/quickstart#creating-a-project), if you haven't already.
+To leverage Depot locally, [install the `depot` CLI tool](/docs/cli/installation) and [configure your Depot project](/docs/container-builds/quickstart#creating-a-project), if you haven't already.
 
 With those two things complete, you can then login to Depot via the CLI:
 

content/integrations/buildkite.mdx

@@ -22,7 +22,7 @@ You can inject a user access token into the pipeline for `depot` CLI authenticat
 
 ## Configuration
 
-To build a Docker image from Buildkite, you must either configure an OIDC trust relationship for your project or set the `DEPOT_TOKEN` environment variable via a Buildkite [`environment` hook](https://buildkite.com/docs/pipelines/secrets#exporting-secrets-with-environment-hooks).
+To build a Docker image from Buildkite, you must either configure an OIDC trust relationship for your project or set the `DEPOT_TOKEN` environment variable via a Buildkite [`environment` hook](https://buildkite.com/docs/pipelines/security/secrets/managing#exporting-secrets-with-environment-hooks).
 
 This guide also assumes that you are defining a `pipeline.yml` configuration file located in a `.buildkite` directory at the root of your repository. See the [Buildkite documentation](https://buildkite.com/docs/pipelines/defining-steps#step-defaults-pipeline-dot-yml-file) for more information on how to configure your pipeline this way.
 
@@ -52,7 +52,7 @@ steps:
 
 ### Build and push to Docker Hub
 
-This example assumes you have set the `DOCKERHUB_USERNAME` and `DOCKERHUB_TOKEN` environment variables as part of the [`environment` hook](https://buildkite.com/docs/pipelines/secrets#exporting-secrets-with-environment-hooks) and you have the `docker` CLI installed in your Buildkite agent.
+This example assumes you have set the `DOCKERHUB_USERNAME` and `DOCKERHUB_TOKEN` environment variables as part of the [`environment` hook](https://buildkite.com/docs/pipelines/security/secrets/managing#exporting-secrets-with-environment-hooks) and you have the `docker` CLI installed in your Buildkite agent.
 
 We then install the `depot` CLI to be used directly in the pipeline. Then, `docker login` is invoked with the environment variables for `DOCKERHUB_USERNAME` and `DOCKERHUB_TOKEN` for the authentication context of the build to push to the registry.
 

content/integrations/fly.mdx

@@ -8,7 +8,7 @@ You can use Depot to build your container images for Fly.io. This guide will sho
 
 ## Getting started with Fly.io
 
-Once you have a Fly.io account, you can create and deploy a new app using the Fly CLI. You can install the Fly CLI using the methods described in the [Fly.io documentation](https://fly.io/docs/hands-on/install-flyctl/).
+Once you have a Fly.io account, you can create and deploy a new app using the Fly CLI. You can install the Fly CLI using the methods described in the [Fly.io documentation](https://fly.io/docs/flyctl/install/).
 
 Once an app is created in Fly.io, you will also have a container registry at `registry.fly.io/<your-app-name>`. You can push your container images to Fly.io from Depot.