formatting

Author: rosieyohannan

jekyll/_cci2/install-machine-runner-3-on-docker.adoc

@@ -15,10 +15,12 @@ contentTags:
 
 This page describes how to install CircleCI's machine runner 3.0 with the Docker executor. If you are looking to set up self-hosted runners in a private Kubernetes cluster, visit the <<container-runner-installation#,Container runner>> page.
 
-[#new-recommended-method-container-runner]
-== Recommended method for Docker installation (container runner)
+[NOTE]
+====
+xref:container-runner#[Container runner] is the **recommended method** for self-hosted runner Docker installation. The instructions on this page are for a simple Docker setup using machine runner 3.0.
 
-The <<container-runner#,container runner>> is the recommended approach for running containerized jobs on self-hosted runners. Container runner offers the ability to seamlessly define, publish, and use custom Docker images during job execution, as well as the ability to manage dependencies or libraries through custom Docker images instead of enumerating dependencies as part of `steps` in the `.circleci/config.yml` file.
+Container runner is the recommended approach for running containerized jobs on self-hosted runners. Container runner offers the ability to seamlessly define, publish, and use custom Docker images during job execution, as well as the ability to manage dependencies or libraries through custom Docker images instead of enumerating dependencies as part of `steps` in the `.circleci/config.yml` file.
+====
 
 [#machine-approach-with-docker]
 == Machine-based approach with Docker
@@ -28,8 +30,8 @@ The <<container-runner#,container runner>> is the recommended approach for runni
 
 * link:https://docs.docker.com/engine/install/[Docker]
 
-[#additional-prerequisites]
-==== Additional prerequisites with Docker
+[#resource-requirements]
+==== Resource requirements
 
 The host needs to have Docker installed. Once the `runner` container is started, the container will immediately attempt to start running jobs. The container will be reused to run more jobs indefinitely until it is stopped.
 
@@ -68,20 +70,23 @@ docker build --file ./Dockerfile.runner.extended .
 
 NOTE: The environment variable values are not available to the `docker` command, so these environment variables are not visible in `ps` output.
 
+[.tab.startContainer.Cloud]
+--
 ```shell
 CIRCLECI_RUNNER_NAME=<runner-name> CIRCLECI_RUNNER_API_AUTH_TOKEN=<runner-token> docker run --env CIRCLECI_RUNNER_NAME --env CIRCLECI_RUNNER_API_AUTH_TOKEN --name <container-name> <image-id-from-previous-step>
 ```
+--
 
-When the container starts, it will immediately attempt to start running jobs.
-
-[#start-the-docker-container-on-server]
-==== Start the Docker container on server
-
+[.tab.startContainer.Server]
+--
 When starting the Docker container on server, the `CIRCLECI_RUNNER_API_URL` environment variable will also need to be passed in using the `--env` flag.
 
 ```shell
 CIRCLECI_RUNNER_NAME=<runner-name> CIRCLECI_RUNNER_API_AUTH_TOKEN=<runner-token> CIRCLECI_RUNNER_API_URL=<server_host_name> docker run --env CIRCLECI_RUNNER_NAME --env CIRCLECI_RUNNER_API_AUTH_TOKEN --env CIRCLECI_RUNNER_API_URL --name <container-name> <image-id-from-previous-step>
 ```
+--
+
+When the container starts, it will immediately attempt to start running jobs.
 
 [#stopping-the-docker-container]
 === Stopping the Docker container