diff --git a/content/actions/sharing-automations/creating-actions/dockerfile-support-for-github-actions.md b/content/actions/sharing-automations/creating-actions/dockerfile-support-for-github-actions.md
index 22e48b624d..796517bae0 100644
--- a/content/actions/sharing-automations/creating-actions/dockerfile-support-for-github-actions.md
+++ b/content/actions/sharing-automations/creating-actions/dockerfile-support-for-github-actions.md
@@ -11,7 +11,7 @@ versions:
   ghec: '*'
 type: reference
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## About Dockerfile instructions
@@ -110,4 +110,4 @@ If you use `CMD` in your `Dockerfile`, follow these guidelines:
 
 ## Supported Linux capabilities
 
-{% data variables.product.prodname_actions %} supports the default Linux capabilities that Docker supports. Capabilities can't be added or removed. For more information about the default Linux capabilities that Docker supports, see "[Runtime privilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" in the Docker documentation. To learn more about Linux capabilities, see "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)" in the Linux man-pages.
+{% data variables.product.prodname_actions %} supports the default Linux capabilities that Docker supports. Capabilities can't be added or removed. For more information about the default Linux capabilities that Docker supports, see "[Linux kernel capabilities](https://docs.docker.com/engine/security/#linux-kernel-capabilities)" in the Docker documentation. To learn more about Linux capabilities, see "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)" in the Linux man-pages.
diff --git a/content/actions/use-cases-and-examples/using-containerized-services/about-service-containers.md b/content/actions/use-cases-and-examples/using-containerized-services/about-service-containers.md
index 4b97069754..3cfba7b219 100644
--- a/content/actions/use-cases-and-examples/using-containerized-services/about-service-containers.md
+++ b/content/actions/use-cases-and-examples/using-containerized-services/about-service-containers.md
@@ -15,7 +15,7 @@ topics:
   - Containers
   - Docker
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## About service containers
@@ -32,7 +32,7 @@ You can configure jobs in a workflow to run directly on a runner machine or in a
 
 ### Running jobs in a container
 
-When you run jobs in a container, {% data variables.product.prodname_dotcom %} connects service containers to the job using Docker's user-defined bridge networks. For more information, see "[Use bridge networks](https://docs.docker.com/network/bridge/)" in the Docker documentation.
+When you run jobs in a container, {% data variables.product.prodname_dotcom %} connects service containers to the job using Docker's user-defined bridge networks. For more information, see "[Bridge network driver](https://docs.docker.com/engine/network/drivers/bridge/)" in the Docker documentation.
 
 Running the job and services in a container simplifies network access. You can access a service container using the label you configure in the workflow. The hostname of the service container is automatically mapped to the label name. For example, if you create a service container with the label `redis`, the hostname of the service container is `redis`.