Merge pull request circleci#8739 from circleci/fix

Style fixes

Author: rosieyohannan

jekyll/_cci2/runner-installation-linux.adoc

@@ -13,16 +13,16 @@ contentTags:
 :machine:
 :linux:
 
-CAUTION: This installation method is deprecated for **CIrcleCI cloud** customers. Refer to the xref:install-machine-runner-3-on-linux#[machine runner 3.0 installation guide] for the recommended steps to set up Linux self-hosted runners on CircleCI cloud.
- 
-This page describes how to install CircleCI's machine runner on Linux for **CircleCI server** customers. 
+CAUTION: This installation method is deprecated for **CircleCI cloud** customers. Refer to the xref:install-machine-runner-3-on-linux#[machine runner 3.0 installation guide] for the recommended steps to set up Linux self-hosted runners on CircleCI cloud.
+
+This page describes how to install CircleCI's machine runner on Linux for **CircleCI server** customers.
 
 [#prerequisites]
 == Prerequisites
 
 To install machine runners and run jobs, you will need to have root access, and have the following utilities and tools installed on your system:
 
-* https://www.gnu.org/software/coreutils/[coreutils]
+* https://www.gnu.org/software/coreutils/[Coreutils]
 
 * https://curl.se/[curl]
 
@@ -32,11 +32,11 @@ To install machine runners and run jobs, you will need to have root access, and
 
 * https://www.gnu.org/software/tar/[tar]
 
-* https://www.gnu.org/software/gzip/[gzip]
+* https://www.gnu.org/software/gzip/[Gzip]
 
-* sepolicy (https://www.redhat.com/en/enterprise-linux-8/details[RHEL 8] only)
+* `sepolicy` (https://www.redhat.com/en/enterprise-linux-8/details[RHEL 8] only)
 
-* rpmbuild (https://www.redhat.com/en/enterprise-linux-8/details[RHEL 8] only)
+* `rpmbuild` (https://www.redhat.com/en/enterprise-linux-8/details[RHEL 8] only)
 
 * The xref:local-cli#[CircleCI CLI] if you wish to install runners from the command line
 
@@ -66,7 +66,7 @@ To install machine runners and run jobs, you will need to have root access, and
 [#create-the-circleci-user-and-working-directory]
 == 3. Create `circleci` user and working directory
 
-These will be used when executing the task-agent. These commands must be run as a user with permissions to create other users (e.g. `root`). For information about GECOS, see the https://en.wikipedia.org/wiki/Gecos_field[wiki page].
+These will be used when executing the task-agent. These commands must be run as a user with permissions to create other users (for example, `root`). For information about GECOS, see the https://en.wikipedia.org/wiki/Gecos_field[wiki page].
 
 [#ubuntu-debian]
 === Ubuntu/Debian
@@ -221,7 +221,7 @@ TimeoutStopSec=18300
 WantedBy = multi-user.target
 ```
 
-Unlike task-agents, which use the environment of the `circleci` user, launch-agents will need to have any required environment variables (e.g., proxy settings) explicitly defined in the unit configuration file. These can be set by `Environment=` or `EnvironmentFile=`. Please visit the `systemd` https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Environment[documentation] for more information.
+Unlike task-agents, which use the environment of the `circleci` user, launch-agents will need to have any required environment variables (for example, proxy settings) explicitly defined in the unit configuration file. These can be set by `Environment=` or `EnvironmentFile=`. Visit the `systemd` https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Environment[documentation] for more information.
 
 You can now enable the service:
 

jekyll/_cci2/runner-installation-mac.adoc

@@ -13,9 +13,9 @@ contentTags:
 :machine:
 :macos:
 
-CAUTION: This installation method is deprecated for **CIrcleCI cloud** customers. Refer to the xref:install-machine-runner-3-on-linux#[machine runner 3.0 installation guide] for the recommended steps to set up macOS self-hosted runners on CircleCI cloud.
+CAUTION: This installation method is deprecated for **CircleCI cloud** customers. Refer to the xref:install-machine-runner-3-on-linux#[machine runner 3.0 installation guide] for the recommended steps to set up macOS self-hosted runners on CircleCI cloud.
 
-This page describes how to install CircleCI's machine runner on macOS for **CircleCI server** customers. 
+This page describes how to install CircleCI's machine runner on macOS for **CircleCI server** customers.
 
 [#prerequisites]
 == Prerequisites

jekyll/_cci2/runner-installation-windows.adoc

@@ -13,7 +13,7 @@ contentTags:
 :machine:
 :windows:
 
-CAUTION: This installation method is deprecated for **CIrcleCI cloud** customers. Refer to the xref:install-machine-runner-3-on-windows#[machine runner 3.0 installation guide] for the recommended steps to set up Windows self-hosted runners on CircleCI cloud.
+CAUTION: This installation method is deprecated for **CircleCI cloud** customers. Refer to the xref:install-machine-runner-3-on-windows#[machine runner 3.0 installation guide] for the recommended steps to set up Windows self-hosted runners on CircleCI cloud.
 
 This page describes how to install machine runner on Windows for **CircleCI server**. This has been tested for Windows Server 2019 and Windows Server 2016, both in Datacenter Edition. Other Server SKUs with Desktop Experience and Remote Desktop Services should also work.
 
@@ -29,7 +29,7 @@ Since this setup creates a new local administrator user that runs CircleCI jobs,
 
 * https://www.gnu.org/software/tar/[tar]
 
-* https://www.gnu.org/software/gzip/[gzip]
+* https://www.gnu.org/software/gzip/[Gzip]
 
 * The xref:local-cli#[CircleCI CLI] if you wish to install runners from the command line
 
@@ -74,7 +74,7 @@ Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManage
 +
 The installation will be output into your PowerShell interface.
 
-. As part of the installation, the configuration file for the machine runner (`launch-agent-config.yaml`) will open in Notepad. Please fill the file out with the requested information (see xref:runner-config-reference.adoc[Self-hosted Runner Configuration Reference]). The configuration file is located in the installation directory, `C:\Program Files\CircleCI`, by default.
+. As part of the installation, the configuration file for the machine runner (`launch-agent-config.yaml`) will open in Notepad. Fill the file out with the requested information (see xref:runner-config-reference.adoc[Self-hosted Runner Configuration Reference]). The configuration file is located in the installation directory, `C:\Program Files\CircleCI`, by default.
 
 After setup completes, the machine runner starts automatically and begins looking for jobs to process.
 
@@ -97,7 +97,7 @@ Uninstalling machine runners will prepare the system for installation again.
 [#continuous-mode-vs.-single-task-mode-for-windows-self-hosted-runners]
 == Continuous mode vs. single task mode for Windows self-hosted runners
 
-By default, Windows machine runners run in <<runner-config-reference#runner-mode,single task mode>> in order to ensure high reliablity of the underlying technology that the self-hosted runner uses to execute jobs. This is the **recommended mode** for Windows machine runners.
+By default, Windows machine runners run in <<runner-config-reference#runner-mode,single task mode>> in order to ensure high reliability of the underlying technology that the self-hosted runner uses to execute jobs. This is the **recommended mode** for Windows machine runners.
 
 A Windows machine runner *can* be run in `continuous` mode, however, doing so eliminates the guarantee of a clean job environment.  This may translate into jobs not executing as expected and failing.
 

styles/config/vocabularies/Docs/accept.txt

@@ -82,6 +82,7 @@ Cypress
 Datacenter
 Datadog
 datastore
+Debian
 deduplicate
 deduplicated
 DevOps
@@ -230,6 +231,7 @@ stdin
 [Ss]ubshells?
 subcommand
 superset
+systemd
 TCPRoute
 TeamCity
 Telegraf
@@ -242,6 +244,7 @@ TLS
 [Tt]oolchains?
 [Tt]ruthy
 TypeScript
+Ubuntu
 UI
 UIDs?
 [Uu]ncheck