chore: add missing language tags for code blocks

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

content/compose/release-notes.md

@@ -3314,7 +3314,8 @@ Thanks @ryanbrainard and @d11wtq!
    For example, if you have a `web` service which depends on a `db` service, `fig run web ...` will start the `db` service.
 
  - Environment variables can now be resolved from the environment that Fig is running in. Just specify it as a blank variable in your `fig.yml` and, if set, it'll be resolved:
-   ```
+
+   ```yaml
    environment:
      RACK_ENV: development
      SESSION_SECRET:
@@ -3322,7 +3323,7 @@ Thanks @ryanbrainard and @d11wtq!
 
  - `volumes_from` is now supported in `fig.yml`. All of the volumes from the specified services and containers will be mounted:
 
-   ```
+   ```yaml
    volumes_from:
     - service_name
     - container_name
@@ -3330,7 +3331,7 @@ Thanks @ryanbrainard and @d11wtq!
 
  - A host address can now be specified in `ports`:
 
-   ```
+   ```yaml
    ports:
     - "0.0.0.0:8000:8000"
     - "127.0.0.1:8001:8001"

content/docker-hub/download-rate-limit.md

@@ -41,7 +41,7 @@ manifest requests.
 
 When you issue a pull request and you are over the limit, Docker Hub returns a `429` response code with the following body when the manifest is requested:
 
-```
+```text
 You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limits
 ```
 
@@ -51,7 +51,7 @@ This error message appears in the Docker CLI or in the Docker Engine logs.
 
 Valid API requests to Hub usually include the following rate limit headers in the response:
 
-```
+```text
 ratelimit-limit    
 ratelimit-remaining
 docker-ratelimit-source

content/get-started/02_our_app.md

@@ -31,7 +31,7 @@ Before you can run the application, you need to get the application source code
 
 2. View the contents of the cloned repository. You should see the following files and sub-directories.
 
-   ```
+   ```text
    ├── getting-started-app/
    │ ├── package.json
    │ ├── README.md
@@ -185,4 +185,4 @@ Related information:
 
 Next, you're going to make a modification to your app and learn how to update your running application with a new image. Along the way, you'll learn a few other useful commands.
 
-{{< button text="Update the application" url="03_updating_app.md" >}}
+{{< button text="Update the application" url="03_updating_app.md" >}}

content/get-started/06_bind_mounts.md

@@ -122,7 +122,7 @@ setting, see the topic for [Mac](../desktop/settings/mac.md/#file-sharing),
 7. Open the `getting-started-app` directory on the host and observe that the
    `myfile.txt` file is in the directory.
 
-   ```
+   ```text
    ├── getting-started-app/
    │ ├── Dockerfile
    │ ├── myfile.txt

content/get-started/08_using_compose.md

@@ -18,16 +18,16 @@ on GitHub/GitLab doing exactly this now.
 
 In the `getting-started-app` directory, create a file named `compose.yaml`.
 
-   ```
-   ├── getting-started-app/
-   │ ├── Dockerfile
-   │ ├── compose.yaml
-   │ ├── node_modules/
-   │ ├── package.json
-   │ ├── spec/
-   │ ├── src/
-   │ └── yarn.lock
-   ```
+```text
+├── getting-started-app/
+│ ├── Dockerfile
+│ ├── compose.yaml
+│ ├── node_modules/
+│ ├── package.json
+│ ├── spec/
+│ ├── src/
+│ └── yarn.lock
+```
 
 ## Define the app service
 
@@ -286,4 +286,4 @@ Related information:
 
 Next, you'll learn about a few best practices you can use to improve your Dockerfile.
 
-{{< button text="Image-building best practices" url="09_image_best.md" >}}
+{{< button text="Image-building best practices" url="09_image_best.md" >}}

content/network/network-tutorial-standalone.md

@@ -604,7 +604,7 @@ connected to both networks.
 
 9.  Stop and remove all containers and the `alpine-net` network.
 
-    ```
+    ```console
     $ docker container stop alpine1 alpine2 alpine3 alpine4
 
     $ docker container rm alpine1 alpine2 alpine3 alpine4
@@ -620,4 +620,4 @@ you might want to run through these other networking tutorials:
 
 - [Host networking tutorial](network-tutorial-host.md)
 - [Overlay networking tutorial](network-tutorial-overlay.md)
-- [Macvlan networking tutorial](network-tutorial-macvlan.md)
+- [Macvlan networking tutorial](network-tutorial-macvlan.md)

content/scout/advisory-db-sources.md

@@ -76,7 +76,7 @@ This can return a lot of false positives which you need to triage.
 
 The typical structure of a CPE match looks like this:
 
-```
+```text
 cpe:<cpe_version>:<part>:<vendor>:<product>:<version>:<update>:<edition>:<language>:<sw_edition>:<target_sw>:<target_hw>:<other>
 ```
 
@@ -93,7 +93,7 @@ identify the relevant packages with far less false positives.
 Continuing this example, a PURL can match the specific package name to a
 language and version.
 
-```
+```text
 pkg:npm/calendar@12.0.2
 ```