From 06b710d24a4244b04da1b8160959716375d59338 Mon Sep 17 00:00:00 2001 From: Nick Santos Date: Thu, 15 Feb 2024 08:49:14 -0500 Subject: [PATCH] build(cloud): rephrase conn encryption improving the phrasing here to be more accurate follow up from https://github.com/docker/docs/pull/19408 Signed-off-by: Nick Santos --- content/build/cloud/_index.md | 2 +- content/build/cloud/usage.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/build/cloud/_index.md b/content/build/cloud/_index.md index d72137d62d..589c5a2a3b 100644 --- a/content/build/cloud/_index.md +++ b/content/build/cloud/_index.md @@ -37,7 +37,7 @@ And the best part: you don't need to worry about managing builders or infrastructure. Just connect to your builders, and start building. Each cloud builder provisioned to an organization is completely isolated to a single Amazon EC2 instance, with a dedicated EBS volume for build -cache, and end-to-end encryption. That means there are no shared processes or +cache, and encryption in transit. That means there are no shared processes or data between cloud builders. > **Note** diff --git a/content/build/cloud/usage.md b/content/build/cloud/usage.md index 1619300e17..08cd15f11a 100644 --- a/content/build/cloud/usage.md +++ b/content/build/cloud/usage.md @@ -136,7 +136,7 @@ and forth between each other. To use build secrets with Docker Build Cloud, such as authentication credentials or tokens, use the `--secret` and `--ssh` CLI flags for the `docker buildx` command. -The traffic is end-to-end encrypted and secrets are never stored in the build cache. +The traffic is encrypted and secrets are never stored in the build cache. > **Warning** >