clean up product name references (#3836)

* clean up product name references

* a few more node fixes

howtos/markdown-and-mdx-features.md

@@ -72,7 +72,7 @@ Template:
 { label: 'Java', value: 'java', },
 { label: 'Java + Spring', value: 'javaspring', },
 { label: 'Kotlin + Spring', value: 'kotlin', },
-{ label: 'NodeJS', value: 'nodejs', },
+{ label: 'Node.js', value: 'nodejs', },
 ] }>
 
 <TabItem value="csharp">

optimize_versioned_docs/version-3.7.0/self-managed/optimize-deployment/migration-update/instructions.md

@@ -88,7 +88,7 @@ For Windows:
 
 This will run the update prior to starting up Optimize and only then start Optimize.
 
-In docker environments this can be achieved by overwriting the default command of the docker container (being `./optimize.sh`), e.g. like in the following [docker-compose](https://docs.docker.com/compose/) snippet:
+In Docker environments this can be achieved by overwriting the default command of the Docker container (being `./optimize.sh`), e.g. like in the following [docker-compose](https://docs.docker.com/compose/) snippet:
 
 ```
 version: '2.4'

optimize_versioned_docs/version-3.7.0/self-managed/optimize-deployment/setup/installation.md

@@ -75,11 +75,11 @@ Login Succeeded
 
 After that, [configure the Elasticsearch connection](#elasticsearch-configuration) to connect to your pre-installed Elasticsearch instance and [configure the Camunda Platform connection](#camunda-platform-configuration) to connect Optimize to your running engine. For very simple use cases with only one Camunda Engine and one Elasticsearch node, you can use environment variables instead of mounting configuration files into the Docker container:
 
-#### Getting started with the Optimize docker image
+#### Getting started with the Optimize Docker image
 
 ##### Full local setup
 
-To start the Optimize docker image and connect to an already locally running Camunda Platform as well as Elasticsearch instance you could run the following command:
+To start the Optimize Docker image and connect to an already locally running Camunda Platform as well as Elasticsearch instance you could run the following command:
 
 ```
 docker run -d --name optimize --network host \

versioned_docs/version-1.3/components/best-practices/architecture/sizing-your-environment.md

@@ -227,5 +227,5 @@ If you are in doubt about which package to choose, you can do a load test with a
 
 This is recommended if you exceed the above numbers of three million process instances per day.
 
-You can look at the [Zeebe benchmark project](https://github.com/camunda/zeebe/blob/1.3.14/benchmarks/setup/README.md#benchmarking-camunda-cloud-saas). While this project will not run out-of-the-box (e.g. you need need to build starter and worker code yourself and use self-created docker images), you can use it as a starting point for own endavours.
+You can look at the [Zeebe benchmark project](https://github.com/camunda/zeebe/blob/1.3.14/benchmarks/setup/README.md#benchmarking-camunda-cloud-saas). While this project will not run out-of-the-box (e.g. you need need to build starter and worker code yourself and use self-created Docker images), you can use it as a starting point for own endavours.
 

versioned_docs/version-1.3/self-managed/zeebe-deployment/configuration/configuration.md

@@ -150,7 +150,7 @@ Update your application's configuration
 
 ## Logging
 
-Zeebe uses Log4j2 framework for logging. In the distribution and the docker image, find the default log configuration file in `config/log4j2.xml`.
+Zeebe uses Log4j2 framework for logging. In the distribution and the Docker image, find the default log configuration file in `config/log4j2.xml`.
 
 ### Google Stackdriver (JSON) logging
 

versioned_docs/version-1.3/self-managed/zeebe-deployment/configuration/logging.md

@@ -3,7 +3,7 @@ id: logging
 title: "Logging"
 ---
 
-Zeebe uses Log4j2 framework for logging. In the distribution and the docker image, find the default log configuration file in `config/log4j2.xml`.
+Zeebe uses Log4j2 framework for logging. In the distribution and the Docker image, find the default log configuration file in `config/log4j2.xml`.
 
 ## Google Stackdriver (JSON) logging
 

versioned_docs/version-1.3/self-managed/zeebe-deployment/docker/install.md

@@ -18,7 +18,7 @@ The easiest way to develop with Zeebe is using Docker. Docker provides a consist
 
 ### Docker configurations for docker-compose
 
-A default docker compose configuration to run Zeebe, Operate, and Tasklist is available in the get started repository: [docker-compose.yaml](https://github.com/camunda-cloud/camunda-cloud-get-started/blob/master/docker-compose.yaml).
+A default Docker Compose configuration to run Zeebe, Operate, and Tasklist is available in the get started repository: [docker-compose.yaml](https://github.com/camunda-cloud/camunda-cloud-get-started/blob/master/docker-compose.yaml).
 
 Download this file to your local computer, `cd` into that directory, and run `docker-compose up`.
 

versioned_docs/version-1.3/self-managed/zeebe-deployment/kubernetes/helm/installing-helm.md

@@ -11,7 +11,7 @@ The Camunda Cloud Helm chart is currently available and can be found in the [Cam
 By default, the following will be installed:
 
 - **Camunda Cloud self-managed Helm (ccsm-helm)**: 
- - **Zeebe**: Deploys a Zeebe Cluster with three brokers using the `camunda/zeebe` docker image.
+ - **Zeebe**: Deploys a Zeebe Cluster with three brokers using the `camunda/zeebe` Docker image.
  - **Zeebe Gateway**: Deploys the standalone Zeebe Gateway with two replicas.
  - **Operate**: Deploys Operate, which connects to an existing Elasticsearch.
  - **Tasklist**: Deploys the Tasklist component to work with user tasks.