GITBOOK-9162: Broker: Derived Docker images to Custom Docker images, title and headings

Author: awileysnyk

docs/SUMMARY.md

@@ -144,7 +144,7 @@
           * [Jira - install and configure using Docker](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/jira-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-jira.md)
           * [Jira - install and configure using Helm](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/jira-prerequisites-and-steps-to-install-and-configure-broker/jira-install-and-configure-using-helm.md)
           * [Jira - environment variables for Snyk Broker](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/jira-prerequisites-and-steps-to-install-and-configure-broker/jira-environment-variables-for-snyk-broker.md)
-        * [Derived Docker images for Broker Client integrations and Container Registry Agent](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md)
+        * [Custom Docker images for Broker Client integrations and Container Registry Agent](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md)
         * [Advanced configuration for Snyk Broker Docker installation](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/README.md)
           * [Changing the auth method with Docker](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/changing-the-auth-method-with-docker.md)
           * [Credential pooling with Docker and Helm](enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/advanced-configuration-for-snyk-broker-docker-installation/credential-pooling-with-docker-and-helm.md)

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/artifactory-repository-install-and-configure-broker/set-up-snyk-broker-with-artifactory-repository.md

@@ -45,7 +45,7 @@ docker run --restart=always \
   snyk/broker:artifactory
 ```
 
-As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the Artifactory integration.
+As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the Artifactory integration.
 
 ## Start the Broker Client container and verify the connection with Artifactory Repository
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/azure-repos-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-azure-repos.md

@@ -43,7 +43,7 @@ docker run --restart=always \
        snyk/broker:azure-repos
 ```
 
-As an **alternative to using the Docker run command,** you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the Azure Repos integration.
+As an **alternative to using the Docker run command,** you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the Azure Repos integration.
 
 ## Start the Broker Client container and verify the connection with Azure Repos
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/bitbucket-server-data-center-prerequisites-and-steps-to-install-and-configure-broker/data-center.md

@@ -44,7 +44,7 @@ docker run --restart=always \
 Snyk Essentials is set by default to **`false`**. Enable it by setting the flag to **`true`**.
 {% endhint %}
 
-As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the BitBucket Server/Data Center integration.
+As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the BitBucket Server/Data Center integration.
 
 ## Configure Broker to be used with Bitbucket using a Personal Access Token (PAT)
 
@@ -77,7 +77,7 @@ docker run --restart=always \
 Snyk Essentials is set by default to **`false`**. Enable it by setting the flag to **`true`**.
 {% endhint %}
 
-As an alternative to using the Docker run command, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the BitBucket Server/Data Center integration.
+As an alternative to using the Docker run command, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the BitBucket Server/Data Center integration.
 
 ## Start the Broker Client container and verify the connection with Bitbucket
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md renamed to docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md

@@ -1,10 +1,10 @@
-# Derived Docker images for Broker Client integrations and Container Registry Agent
+# Custom Docker images for Broker Client integrations and Container Registry Agent
 
 {% hint style="info" %}
-Using the information on this page is not required to set up Broker Client integrations. You may use a derived Docker image to set up a Broker Client integration. This is an alternative to running the command explained in the instructions for setting up each integration.
+Using the information on this page is not required to set up Broker Client integrations. You may use a custom Docker image to set up a Broker Client integration. This is an alternative to running the command explained in the instructions for setting up each integration.
 {% endhint %}
 
-## Derived Docker image for Azure Repos Broker integration setup
+## Custom Docker image for Azure Repos Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](azure-repos-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-azure-repos.md), you can build your own Docker image and override relevant environment variables:
 
@@ -19,7 +19,7 @@ ENV BROKER_CLIENT_URL   http://my.broker.client:8000
 ENV PORT                8000
 ```
 
-## Derived Docker image for Bitbucket Server/Data Center Broker integration setup
+## Custom Docker image for Bitbucket Server/Data Center Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](bitbucket-server-data-center-prerequisites-and-steps-to-install-and-configure-broker/data-center.md), you can build your own Docker image and override relevant environment variables:
 
@@ -34,7 +34,7 @@ ENV BITBUCKET_API       your.bitbucket-server.domain.com/rest/api/1.0
 ENV PORT                8000
 ```
 
-## Derived Docker image for GitHub Broker integration setup
+## Custom Docker image for GitHub Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](github-prerequisites-and-steps-to-install-and-configure-broker/github-install-and-configure-using-docker.md), you can build your own Docker image and override relevant environment variables:
 
@@ -47,7 +47,7 @@ ENV PORT              8000
 ENV BROKER_CLIENT_URL http://my.broker.client:8000
 ```
 
-## Derived Docker image for GitHub Enterprise Broker integration setup
+## Custom Docker image for GitHub Enterprise Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](github-enterprise-prerequisites-and-steps-to-install-and-configure-broker/github-enterprise-install-and-configure-using-docker.md), you can build you own Docker image and override relevant environment variables:
 
@@ -63,7 +63,7 @@ ENV PORT              8000
 ENV BROKER_CLIENT_URL http://my.broker.client:8000
 ```
 
-## Derived Docker image for GitLab Broker integration setup
+## Custom Docker image for GitLab Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](gitlab-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-gitlab.md), you can build your own Docker image and override relevant environment variables:
 
@@ -77,7 +77,7 @@ ENV BROKER_CLIENT_URL   http://my.broker.client:8000
 ENV PORT                8000
 ```
 
-## Derived Docker image for Jira Broker integration setup
+## Custom Docker image for Jira Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](jira-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-jira.md), you can build your own Docker image and override relevant environment variables:
 
@@ -91,7 +91,7 @@ ENV JIRA_HOSTNAME       your.jira.domain.com
 ENV PORT                8000
 ```
 
-## Derived Docker image for Artifactory Broker integration setup
+## Custom Docker image for Artifactory Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](artifactory-repository-install-and-configure-broker/set-up-snyk-broker-with-artifactory-repository.md), you can build your own Docker image and override relevant environment variables:
 
@@ -102,7 +102,7 @@ ENV BROKER_TOKEN      secret-broker-token
 ENV ARTIFACTORY_URL   <yourdomain>.artifactory.com
 ```
 
-## Derived Docker image for Nexus 3 Broker integration setup
+## Custom Docker image for Nexus 3 Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](nexus-repository-prerequisites-and-steps-to-install-and-configure-broker/set-up-snyk-broker-with-nexus-repository-manager.md), you can build your own Docker image and override relevant environment variables:
 
@@ -120,7 +120,7 @@ ENV RES_BODY_URL_SUB                 https://<your.nexus.hostname>/repository
 By default for Nexus 3, the X-Forwarded-For headers are stripped off by the Broker Client so Nexus returns the npm tarball uri to the Nexus Registry instead of the Broker Server. Include the environment variable `REMOVE_X_FORWARDED_HEADERS=false` to disable this behavior.
 {% endhint %}
 
-## Derived Docker image for Nexus 2 Broker integration setup
+## Custom Docker image for Nexus 2 Broker integration setup
 
 As an alternative to using the Docker run command shown on the [setup page](nexus-repository-prerequisites-and-steps-to-install-and-configure-broker/set-up-snyk-broker-with-nexus-repository-manager.md), you can build your own Docker image and override relevant environment variables:
 
@@ -137,7 +137,7 @@ ENV RES_BODY_URL_SUB                 https://<your.nexus.hostname>/nexus/content
 By default for Nexus 2, the X-Forwarded-For headers are stripped off by the Broker Client so Nexus returns the npm tarball uri to the Nexus Registry instead of the Broker Server. Include the environment variable REMOVE\_X\_FORWARDED\_HEADERS=false to disable this behavior.
 {% endhint %}
 
-## Derived Docker image for Container Registry Agent setup
+## Custom Docker image for Container Registry Agent setup
 
 As an alternative to using the Docker run command shown on the [setup page](../../snyk-broker-container-registry-agent/), you can build your own Docker image and override relevant environment variables:
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/github-enterprise-prerequisites-and-steps-to-install-and-configure-broker/github-enterprise-install-and-configure-using-docker.md

@@ -40,7 +40,7 @@ docker run --restart=always \
 Snyk Essentials is set by default to **`false`**. Enable it by setting the flag to **`true`**.
 {% endhint %}
 
-As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the GitHub Enterprise integration.
+As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the GitHub Enterprise integration.
 
 ## Start the Broker Client container and verify the connection with GitHub Enterprise
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/github-prerequisites-and-steps-to-install-and-configure-broker/github-install-and-configure-using-docker.md

@@ -37,7 +37,7 @@ docker run --restart=always \
 Snyk Essentials is set by default to **`false`**. Enable it by setting the flag to **`true`**.
 {% endhint %}
 
-As an **alternative using to the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the GitHub integration.
+As an **alternative using to the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the GitHub integration.
 
 ## Start the Broker Client container and verify the connection with GitHub
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/gitlab-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-gitlab.md

@@ -38,7 +38,7 @@ Use the environment variable `REMOVE_X_FORWARDED_HEADERS=true` to remove the `XF
 
 Snyk Essentials is set by default to `false`. Enable it by setting the flag to `true`.
 
-As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the GitLab integration.
+As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the GitLab integration.
 
 ## Start the Broker Client container and verify the connection with GitLab
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/install-and-configure-broker-using-docker.md

@@ -28,7 +28,7 @@ The following pages explain how to install these special integrations.
 * [Nexus Repository Manager](nexus-repository-prerequisites-and-steps-to-install-and-configure-broker/set-up-snyk-broker-with-nexus-repository-manager.md)
 * [Jira](jira-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-jira.md)
 * [Snyk Broker - Container Registry Agent](../../snyk-broker-container-registry-agent/) (needed to connect to Container Registries)
-* [Derived Docker images for Broker Client integrations and Container Registry Agent](derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md)
+* [Derived Docker images for Broker Client integrations and Container Registry Agent](custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md)
 
 You can customize the configuration using the environment variables in the Docker images. For this reason, install separate, multiple instances of the Broker Client for different integration types to ensure proper configuration as well as redundancy.
 

docs/enterprise-setup/snyk-broker/classic-broker/install-and-configure-snyk-broker/jira-prerequisites-and-steps-to-install-and-configure-broker/setup-broker-with-jira.md

@@ -32,7 +32,7 @@ docker run --restart=always \
 
 If necessary, navigate to [Advanced configuration for Snyk Broker Docker installation](../advanced-configuration-for-snyk-broker-docker-installation/) and make any configuration changes needed, for example, providing the CA (Certificate Authority) to the Broker Client configuration when the Jira instance is using a private certificate.
 
-As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../derived-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the Jira integration.
+As an **alternative to using the Docker run command**, you can use a derived Docker image to set up the Broker Client integration. See [Derived Docker images](../custom-docker-images-for-broker-client-integrations-and-container-registry-agent.md) for the environment variables to override for the Jira integration.
 
 ## Jira PAT authentication for SSO-enabled JIRA