Couple of text updates for the DBC and Compose learning paths (#20718)

content/learning-paths/docker-build-cloud.md

@@ -59,7 +59,8 @@ dimensioned for your workloads, with no configuration required. The service
 uses a remote build cache, ensuring fast builds anywhere and for all team
 members.
 
-- Docker Build Cloud provides several benefits over local builds:
+Docker Build Cloud provides several benefits over local builds:
+
 - Improved build speed
 - Shared build cache
 - Native multi-platform builds
@@ -78,13 +79,14 @@ there are no shared processes or data between cloud builders.
 
 {{< accordion large=true title=`Demo: set up and use Docker Build Cloud in development` icon=`play_circle` >}}
 
-Shift the build workload from local machines to a remote BuildKit instance —
-achieve faster build times, especially for multi-platform builds.
+With Docker Build Cloud, you can easily shift the build workload from local machines 
+to the cloud, helping you achieve faster build times, especially for multi-platform builds.
 
-- Choose the right build: local or cloud?
-- Use with Docker Compose
-- Multi-platform builds
-- Cloud builds in Docker Desktop
+In this demo, you'll see:
+
+- How to setup the builder locally
+- How to use Docker Build Cloud with Docker Compose
+- How the image cache speeds up builds for others on your team
 
 **Duration**: 4 minutes
 
@@ -94,7 +96,18 @@ achieve faster build times, especially for multi-platform builds.
 
 {{< accordion large=true title=`Demo: using Docker Build Cloud in CI` icon=`play_circle` >}}
 
-Speed up your build pipelines — delegate the build execution to Docker Build Cloud in CI.
+Docker Build Cloud can significantly decrease the time it takes for your CI builds
+take to run, saving you time and money. 
+
+Since the builds run remotely, your CI runner can still use the Docker tooling CLI
+without needing elevated permissions, making your builds more secure by default.
+
+In this demo, you will see:
+
+- How to integrate Docker Build Cloud into a variety of CI platforms
+- How to use Docker Build Cloud in GitHub Actions to build multi-architecture images
+- Speed differences between a workflow using Docker Build Cloud and a workflow running natively
+- How to use Docker Build Cloud in a GitLab Pipeline
 
 **Duration**: 4 minutes
 
@@ -135,8 +148,8 @@ subscriber (Personal, Pro, Team, Business), you will also receive your included
 build minutes from that plan.
 
 For example, if a Docker Team customer purchases 5 Build Cloud Team seats, they
-will have 400 minutes from their Docker Team plan plus 1000 minutes (200 min/mo
-* 5 seats) for a total of 1400 minutes per month.
+will have 400 minutes from their Docker Team plan plus 1000 minutes (200 min/mo * 5 seats) 
+for a total of 1400 minutes per month.
 
 ### I’m a Docker personal user. Can I try Docker Build Cloud?
 

content/learning-paths/docker-compose.md

@@ -77,7 +77,7 @@ This Docker Compose demo shows how to orchestrate a multi-container application
 environment, streamlining development and deployment processes.
 
 - Compare Docker Compose to the `docker run` command
-- Configure a multi-container web app using a compose.yml file
+- Configure a multi-container web app using a Compose file
 - Run a multi-container web app using one command
 
 **Duration**: 2.5 minutes
@@ -94,7 +94,7 @@ environment, streamlining development and deployment processes.
 
 You don't necessarily need to maintain entirely separate Compose files for your
 development, testing, and staging environments. You can define all your
-services in a single Compose file (`compose.yml`). You can use profiles to
+services in a single Compose file (`compose.yaml`). You can use profiles to
 group service configurations specific to each environment (`dev`, `test`,
 `staging`).
 
@@ -136,7 +136,7 @@ tool for defining and running multi-container applications. Even if your
 application isn't a multi-container application, Docker Compose can make it
 easier to run by defining all the `docker run` options in a file.
 
-To use Compose, you need a `compose.yml` file. In this file, you can specify
+To use Compose, you need a `compose.yaml` file. In this file, you can specify
 the build context and Dockerfile for each service. When you run the command
 `docker compose up --build`, Docker Compose will build the images for each
 service and then start the containers.