publish updates from main (#22137)

Automated pull request for publishing docs updates.

---------

Co-authored-by: Ville Skyttä <[email protected]>
Co-authored-by: Veck Hsiao <[email protected]>
Co-authored-by: Etienne Guerlain <[email protected]>
Co-authored-by: Manuel de la Peña <[email protected]>
Co-authored-by: aevesdocker <[email protected]>
Co-authored-by: Veesh Goldman <[email protected]>

Author: 6 people

_vale/config/vocabularies/Docker/accept.txt

@@ -55,6 +55,7 @@ Intune
 JFrog
 Jamf
 JetBrains
+JUnit
 Kerberos
 Kitematic
 Kubeadm
@@ -80,6 +81,7 @@ Paketo
 Postgres
 PowerShell
 Python
+Ryuk
 S3
 SQLite
 Slack

content/guides/genai-leveraging-rag/index.md

@@ -38,7 +38,7 @@ The system operates as follows:
 3. The found information gets added to the original question before passed to LLM 
 4. The LLM generates responses that blend the model's inherent knowledge with the this extra information.  
 
-To hold this vector information in a efficient manner, we need a special type of database.
+To hold this vector information in an efficient manner, we need a special type of database.
 
 ## Introduction to Graph databases 
 

content/guides/python/deploy.md

@@ -161,7 +161,7 @@ In these Kubernetes YAML file, there are various objects, separated by the `---`
   your Python application](configure-ci-cd.md).
 - A Service, which will define how the ports are mapped in the containers.
 - A PersistentVolumeClaim, to define a storage that will be persistent through restarts for the database.
-- A Secret, Keeping the database password as a example using secret kubernetes resource.
+- A Secret, Keeping the database password as an example using secret kubernetes resource.
 - A NodePort service, which will route traffic from port 30001 on your host to
   port 8001 inside the pods it routes to, allowing you to reach your app
   from the network.

content/guides/ruby/develop.md

@@ -176,7 +176,7 @@ $ docker compose watch
 
 Any changes to the application's source files on your local machine will now be immediately reflected in the running container.
 
-Open `docker-ruby-on-rails/app/views/whales/index.html.erb` in an IDE or text editor and update the `Whales` string by adding a exclamation marks.
+Open `docker-ruby-on-rails/app/views/whales/index.html.erb` in an IDE or text editor and update the `Whales` string by adding an exclamation mark.
 
 ```diff
 -    <h1>Whales</h1>

content/manuals/_index.md

@@ -26,6 +26,10 @@ params:
     description: Define and run multi-container applications.
     icon: /assets/icons/Compose.svg
     link: /compose/
+  - title: Testcontainers OSS
+    description: Run containers programmatically in your preferred programming language.
+    icon: /assets/icons/Testcontainers.svg
+    link: /testcontainers/
   products:
   - title: Docker Desktop
     description: Your command center for container development.

content/manuals/build/bake/compose-file.md

@@ -10,7 +10,7 @@ Bake supports the [Compose file format](/reference/compose-file/_index.md)
 to parse a Compose file and translate each service to a [target](reference.md#target).
 
 ```yaml
-# docker-compose.yml
+# compose.yaml
 services:
   webapp-dev:
     build: &build-dev
@@ -106,7 +106,7 @@ where the command is executed and applied to compose definitions passed
 with `-f`.
 
 ```yaml
-# docker-compose.yml
+# compose.yaml
 services:
   webapp:
     image: docker.io/username/webapp:${TAG:-v1.0.0}
@@ -152,7 +152,7 @@ the [special extension](/reference/compose-file/extension.md) field
 `x-bake` in your compose file to evaluate extra fields:
 
 ```yaml
-# docker-compose.yml
+# compose.yaml
 services:
   addon:
     image: ct-addon:bar

content/manuals/compose/how-tos/environment-variables/envvars-precedence.md

@@ -30,7 +30,7 @@ In the following example, a different value for the same environment variable in
 $ cat ./webapp.env
 NODE_ENV=test
 
-$ cat compose.yml
+$ cat compose.yaml
 services:
   webapp:
     image: 'webapp'

content/manuals/compose/how-tos/environment-variables/envvars.md

@@ -74,7 +74,7 @@ Specifies the path to a Compose file. Specifying multiple Compose files is suppo
    For example:
 
       ```console
-      COMPOSE_FILE=docker-compose.yml:docker-compose.prod.yml
+      COMPOSE_FILE=compose.yaml:compose.prod.yaml
       ```  
    The path separator can also be customized using [`COMPOSE_PATH_SEPARATOR`](#compose_path_separator).  
 

content/manuals/compose/how-tos/environment-variables/set-environment-variables.md

@@ -20,7 +20,7 @@ A container's environment is not set until there's an explicit entry in the serv
 ## Use the `environment` attribute
 
 You can set environment variables directly in your container's environment with the
-[`environment` attribute](/reference/compose-file/services.md#environment) in your `compose.yml`. 
+[`environment` attribute](/reference/compose-file/services.md#environment) in your `compose.yaml`.
 
 It supports both list and mapping syntax:
 
@@ -74,7 +74,7 @@ It can also help you keep your environment variables separate from your main con
 
 The [`env_file` attribute](/reference/compose-file/services.md#env_file) also lets you use multiple `.env` files in your Compose application.  
 
-The paths to your `.env` file, specified in the `env_file` attribute, are relative to the location of your `compose.yml` file. 
+The paths to your `.env` file, specified in the `env_file` attribute, are relative to the location of your `compose.yaml` file.
 
 > [!IMPORTANT]
 >

content/manuals/compose/how-tos/environment-variables/variable-interpolation.md

@@ -21,7 +21,7 @@ Below is a simple example:
 ```console
 $ cat .env
 TAG=v1.5
-$ cat compose.yml
+$ cat compose.yaml
 services:
   web:
     image: "webapp:${TAG}"
@@ -98,7 +98,7 @@ services:
 
 #### Additional information 
 
-- If you define a variable in your `.env` file, you can reference it directly in your `compose.yml` with the [`environment` attribute](/reference/compose-file/services.md#environment). For example, if your `.env` file contains the environment variable `DEBUG=1` and your `compose.yml` file looks like this:
+- If you define a variable in your `.env` file, you can reference it directly in your `compose.yaml` with the [`environment` attribute](/reference/compose-file/services.md#environment). For example, if your `.env` file contains the environment variable `DEBUG=1` and your `compose.yaml` file looks like this:
    ```yaml
     services:
       webapp:
@@ -163,14 +163,14 @@ $ docker compose --env-file ./config/.env.dev up
 
 #### Additional information 
 
-- This method is useful if you want to temporarily override an `.env` file that is already referenced in your `compose.yml` file. For example you may have different `.env` files for production ( `.env.prod`) and testing (`.env.test`).
+- This method is useful if you want to temporarily override an `.env` file that is already referenced in your `compose.yaml` file. For example you may have different `.env` files for production ( `.env.prod`) and testing (`.env.test`).
   In the following example, there are two environment files, `.env` and `.env.dev`. Both have different values set for `TAG`. 
   ```console
   $ cat .env
   TAG=v1.5
   $ cat ./config/.env.dev
   TAG=v1.6
-  $ cat compose.yml
+  $ cat compose.yaml
   services:
     web:
       image: "webapp:${TAG}"