Update docs content from https://github.com/depot/app

Author: andie787

content/ci/compatibility.mdx

@@ -183,7 +183,7 @@ Custom runner images via the `snapshot` field aren't supported. You can still [b
 
 ### Runner labels
 
-Only Depot `runs-on` labels are supported. Any label that Depot doesn't recognize is treated as `depot-ubuntu-latest`.
+Only Depot `runs-on` labels are supported. Nonstandard labels become `depot-ubuntu-latest` and expressions are preserved as-is. For Depot CI sandbox sizes and labels, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
 
 ### Permissions
 

content/ci/how-to-guides/custom-images.mdx

@@ -89,6 +89,8 @@ Available values for `size`:
 | `32x128` | 32   | 128 GB |
 | `64x256` | 64   | 256 GB |
 
+For sandbox information and pricing, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
+
 ## Environment variable changes don't persist in custom images
 
 For actions that set or change environment variables, you need to include the steps in both the image build workflow and the workflows that use the custom image.

content/ci/overview.mdx

@@ -135,7 +135,7 @@ For the full compatibility matrix, see [Depot CI compatibility with GitHub Actio
 
 ## Pricing
 
-Depot CI sandbox usage is tracked and billed by the second, with no one-minute minimum per run. The minutes included with each plan are based on the smallest sandbox size (2 CPUs/8 GB). See [Depot CI sandbox sizes](#depot-ci-sandbox-sizes).
+Depot CI sandbox usage is tracked and billed by the second, with no one-minute minimum per run. The minutes included with each plan are based on the smallest sandbox size (2 CPUs/8 GB). The included plan minutes aren't a hard cap. Additional usage is billed automatically. For sandbox sizes and additional usage pricing, see [Depot CI sandboxes](#depot-ci-sandboxes).
 
 |                      | Developer plan                                      | Startup plan                                         | Business plan |
 | -------------------- | --------------------------------------------------- | ---------------------------------------------------- | ------------- |
@@ -151,13 +151,13 @@ Depot CI sandbox usage is tracked and billed by the second, with no one-minute m
 
 Plans also include [container build](/docs/container-builds/overview) minutes and [GitHub Actions runner](/docs/github-actions/overview) minutes. See [Pricing](/pricing) for more about plan features and costs.
 
-The Depot CI minutes included in your monthly plan are not a hard cap. Additional usage is billed automatically.
+## Depot CI sandboxes
 
-### Depot CI sandbox sizes
+Depot CI runs your workflows in x86_64 sandboxes. Sandboxes can use from 2 CPUs/8 GB of memory up to 64 CPUs/256 GB of memory. The default sandbox image is based on Ubuntu 24.04.
 
-Larger sandboxes consume your included Depot CI minutes faster and cost more per second for extra usage. For example, a 4-CPU sandbox uses 2 minutes for every 1 minute of running time.
+Larger sandboxes consume the Depot CI minutes included in your plan faster and cost more per second for extra usage. For example, a 4-CPU sandbox uses 2 minutes for every 1 minute of running time.
 
-Use the labels from the following table in the `runs-on` key of your workflow. Use the sandbox size when referencing a [custom image](/docs/ci/how-to-guides/custom-images).
+Use a _Label_ from the following table in the `runs-on` key of your workflow. For [custom images](/docs/ci/how-to-guides/custom-images), use a _Sandbox size_ paired with a Depot Registry custom image URL in the `runs-on` key.
 
 | Label                   | Sandbox size | CPUs | Memory | Per-second price | Plan minutes multiplier |
 | :---------------------- | :----------- | :--- | :----- | :--------------- | :---------------------- |
@@ -168,6 +168,8 @@ Use the labels from the following table in the `runs-on` key of your workflow. U
 | `depot-ubuntu-24.04-32` | `32x128`     | 32   | 128 GB | $0.0016          | 16x                     |
 | `depot-ubuntu-24.04-64` | `64x256`     | 64   | 256 GB | $0.0032          | 32x                     |
 
+Depot CI doesn't provide sandboxes for Arm, macOS, or Windows. Labels for these runner types (as listed in [Depot GitHub Actions runner types](/docs/github-actions/runner-types)) aren't compatible with Depot CI.
+
 ## FAQ
 
 <FAQSection>

content/ci/quickstart.mdx

@@ -57,12 +57,16 @@ The command runs a preflight check, then copies and transforms your workflows:
 1. Validates authentication and checks that the [Depot Code Access app](#connect-to-github) is installed with the correct permissions.
 2. Discovers all workflow files in `.github/workflows/`.
 3. Prompts you to select which workflows to migrate.
-4. Copies selected workflows to `.depot/workflows/` and any local actions to `.depot/actions/`, applying compatibility fixes and adding inline comments for any changes.
+4. Copies selected workflows to `.depot/workflows/` and any local actions to `.depot/actions/`, applies compatibility fixes, and adds inline comments for any changes.
 
 After migration, the command reports any secrets and variables referenced by the migrated workflows. To import them, see [Import secrets and variables](#import-secrets-and-variables) below.
 
 For a full description of flags and subcommands, see [`depot ci migrate`](/docs/cli/reference/depot-ci#depot-ci-migrate) in the Depot CLI reference.
 
+### Sandbox sizes
+
+The `depot ci migrate` command changes standard `ubuntu-24.x` or `ubuntu-latest` runner labels in your workflow to the equivalent Depot CI sandbox label and notes the change in the migrated file. Nonstandard labels become `depot-ubuntu-latest` and expressions are preserved as-is. For Depot CI sandbox sizes and labels, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
+
 ## Import secrets and variables
 
 If your workflows reference GitHub secrets or variables, use `depot ci migrate secrets-and-vars` to import them into Depot CI:
@@ -71,7 +75,7 @@ If your workflows reference GitHub secrets or variables, use `depot ci migrate s
 depot ci migrate secrets-and-vars
 ```
 
-This creates a one-shot GitHub Actions workflow that reads your existing GitHub secrets and variables and imports them into Depot CI. The command prints a URL where you can monitor the import.
+This command creates a one-shot GitHub Actions workflow that reads your existing GitHub secrets and variables and imports them into Depot CI. The command prints a URL where you can monitor the import.
 
 You can also add secrets and variables manually with `depot ci secrets add` and `depot ci vars add`, or from the [Depot CI settings](https://depot.dev/orgs/_/workflows/settings) in the dashboard. See [Manage secrets and variables](/docs/ci/how-to-guides/manage-secrets-and-variables) for details.
 

content/container-builds/build-parallelism.mdx

@@ -121,7 +121,7 @@ When the same instruction is being built multiple times on the same runner, you
 
 When Build A starts building at 10:00 AM, it pulls the base image and runs `npm ci`, creating new layers. When Build B starts building just a minute later at 10:01 AM, BuildKit recognizes that it needs the same base image and has the same `npm ci` command. Instead of duplicating this work, Build B waits for Build A to complete those steps, then reuses the layers that Build A created.
 
-The deduplication process generally improves overall efficiency, but can be confusing when monitoring individual build times. To avoid overwhelming a single build server, you can enable [build auto-scaling](./how-to-guides/autoscaling) to some particular maximum parallelism value.
+The deduplication process generally improves overall efficiency, but can be confusing when monitoring individual build times. To avoid overwhelming a single build server, you can enable [build auto-scaling](/docs/container-builds/how-to-guides/autoscaling) to some particular maximum parallelism value.
 
 #### Docker Bake for orchestrated builds
 
@@ -195,7 +195,7 @@ Trade-offs:
 
 #### Configuration
 
-For detailed instructions on enabling and configuring auto-scaling, see the [Auto-scaling documentation](./how-to-guides/autoscaling).
+For detailed instructions on enabling and configuring auto-scaling, see the [Auto-scaling documentation](/docs/container-builds/how-to-guides/autoscaling).
 
 **Poor cache performance with auto-scaling**
 

content/github-actions/runner-types.mdx

@@ -1,10 +1,12 @@
 ---
-title: GitHub Actions Runner types
+title: Depot GitHub Actions runner types
 ogTitle: Types of Depot-managed GitHub Action Runners
-description: Depot offers several different types of GitHub Actions runners, depending on your CI job needs.
+description: Depot offers several different types of GitHub Actions runners, depending on your needs.
 ---
 
-Depot offers several different types of GitHub Actions runners, depending on your CI job needs. You can choose the type on a per-job basis by specifying the runner label in your `.github/workflows/*.yaml` file:
+This page lists Depot GitHub Actions runner types and sizes. For Depot CI, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
+
+Depot offers several different types of GitHub Actions runners. You can choose the type on a per-job basis by specifying the runner label in your `.github/workflows/*.yaml` file:
 
 ```yaml
 jobs: