ENGDOCS-1580 (#19258)

* ENGDOCS-1580

* tidy

content/compose/compose-file/06-networks.md

@@ -73,7 +73,7 @@ networks:
     driver: overlay
 ```
 
-Default and available values are platform specific. Compose supports the following drivers:
+Compose supports the following drivers:
 `none` and `host`
 
 - `host`: Use the host's networking stack.
@@ -250,4 +250,8 @@ networks:
   network1:
     external: true
     name: "${NETWORK_ID}"
-```
+```
+
+## Additional resources
+
+For more examples, see [Networking in Compose](../networking.md).

content/compose/gpu-support.md

@@ -29,7 +29,7 @@ This provides more granular control over a GPU reservation as custom values can
 > `count` and `device_ids` are mutually exclusive. You must only define one field at a time.
 { .important }
 
-For more information on these properties, see the `deploy` section in the [Compose Specification](compose-file/deploy.md#devices).
+For more information on these properties, see the [Compose Deploy Specification](compose-file/deploy.md#devices).
 
 ### Example of a Compose file for running a service with access to 1 GPU device:
 

content/compose/production.md

@@ -60,7 +60,7 @@ recreating any services which `web` depends on.
 
 You can use Compose to deploy an app to a remote Docker host by setting the
 `DOCKER_HOST`, `DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` environment variables
-appropriately. See also [Compose CLI environment variables](environment-variables/envvars.md).
+appropriately. For more information, see [pre-defined environment variables](environment-variables/envvars.md).
 
 Once you've set up your environment variables, all the normal `docker compose`
 commands work with no further configuration.

content/compose/startup-order.md

@@ -8,7 +8,7 @@ notoc: true
 {{< include "compose-eol.md" >}}
 
 You can control the order of service startup and shutdown with the
-[depends_on](compose-file/05-services.md#depends_on) option. Compose always starts and stops
+[depends_on](compose-file/05-services.md#depends_on) attribute. Compose always starts and stops
 containers in dependency order, where dependencies are determined by
 `depends_on`, `links`, `volumes_from`, and `network_mode: "service:..."`.