build(cloud): move internal/vpn registry info from faq to usage

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>

content/build/cloud/_index.md

@@ -4,6 +4,7 @@ description: Get started with Docker Build Cloud
 keywords: build, cloud, cloud build, remote builder
 aliases:
   - /build/hydrobuild/
+  - /build/cloud/faq/
 ---
 
 Docker Build Cloud is a service that lets you build your container images
@@ -65,8 +66,3 @@ builder in your local environment](./setup.md).
 
 For more information about the available subscription plans, see [Docker Build Cloud
 subscriptions and features](../../subscription/build-details.md).
-
-## Frequently asked questions
-
-The [Docker Build Cloud FAQ](./faq.md) page lists common questions and answers about
-Docker Build Cloud.

content/build/cloud/faq.md

@@ -1,22 +0,0 @@
----
-title: Docker Build Cloud FAQ
-description: Frequently asked questions about Docker Build Cloud
-keywords: build, cloud build, faq, troubleshooting 
-aliases:
-  - /hydrobuild/faq/
----
-
-<!--toc:start-->
-- [How do I remove Docker Build Cloud from my system?](#how-do-i-remove-docker-build-cloud-from-my-system)
-- [Are builders shared between organizations?](#are-builders-shared-between-organizations)
-- [Do I need to add my secrets to the builder to access private resources?](#do-i-need-to-add-my-secrets-to-the-builder-to-access-private-resources)
-- [How do I unset Docker Build Cloud as the default builder?](#how-do-i-unset-docker-build-cloud-as-the-default-builder)
-- [How do I manage the build cache with Docker Build Cloud?](#how-do-i-manage-the-build-cache-with-docker-build-cloud)
-- [Can I use Docker Build Cloud with a registry behind a VPN?](#can-i-use-docker-build-cloud-with-a-registry-behind-a-vpn)
-<!--toc:end-->
-
-### Can I use Docker Build Cloud with a registry behind a VPN?
-
-No, you can't use Docker Build Cloud with a private registry or registry mirror
-behind a VPN. All endpoints invoked with Docker Build Cloud, including OCI
-registries, must be accessible over the internet.

content/build/cloud/usage.md

@@ -183,3 +183,10 @@ $ docker context use default
 
 This doesn't remove the builder from your system.
 It only changes the builder that's automatically selected to run your builds.
+
+## Registries on internal networks
+
+It isn't possible to use Docker Build Cloud with a private registry
+or registry mirror on an internal network behind a VPN.
+All endpoints that a cloud builder interacts with,
+including OCI registries, must be accessible over the internet.

data/toc.yaml

@@ -2175,8 +2175,6 @@ FAQ:
     title: Overview
   - path: /billing/faqs/
     title: Billing
-  - path: /build/cloud/faq/
-    title: Build Cloud
   - path: /compose/faq/
     title: Compose
   - sectiontitle: Desktop