Skip to content

Commit 93ef639

Browse files
Merge pull request #9958 from circleci/fix/docs-typos
Fix spelling and typos across documentation
2 parents f745bbb + 5c9ad62 commit 93ef639

File tree

35 files changed

+41
-41
lines changed

35 files changed

+41
-41
lines changed

docs/guides/modules/ROOT/examples/logic-statement-examples/expression-based-job-filters/multiple-or.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ parameters:
66
default: false
77

88
...
9-
# jobs configuration ommitted for brevity
9+
# jobs configuration omitted for brevity
1010

1111
workflows:
1212
build:

docs/guides/modules/ROOT/partials/runner/install-with-cli-steps.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
//== Command line installation: pre-steps
22

3-
// Display the following step for machine runner installation only as container runner is not yet avaiable on server
3+
// Display the following step for machine runner installation only as container runner is not yet available on server
44
ifdef::machine[]
55
NOTE: If you are installing **self-hosted runners for server**, the CircleCI CLI needs to be configured using your server API key. Run `circleci setup` to configure the CLI and access the option to supply a new API token if required.
66
endif::[]

docs/guides/modules/ROOT/partials/troubleshoot/self-hosted-runner-troubleshoot-snip.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The pod will have a status of `OOMKilled` when viewed in Kubernetes with kubectl
3030
[#pod-host-node-is-out-of-disk-space]
3131
=== Pod host node is out of disk space
3232

33-
If the node is full it will have a `node.kuberenetes.io/disk-pressure` taint, which will prevent new task pods from being scheduled. If all valid nodes for the pod have the same taint, or other conditions that prevent scheduling, the task pod will sit in a pending state until an untainted valid node becomes available. This will show the job as stuck in the **Preparing Environment** step in the UI.
33+
If the node is full it will have a `node.kubernetes.io/disk-pressure` taint, which will prevent new task pods from being scheduled. If all valid nodes for the pod have the same taint, or other conditions that prevent scheduling, the task pod will sit in a pending state until an untainted valid node becomes available. This will show the job as stuck in the **Preparing Environment** step in the UI.
3434

3535
You need to scale your cluster more effectively to avoid this state.
3636

docs/guides/modules/deploy/pages/deploy-to-google-cloud-platform.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ In the following example, if the `build-job` passes and the current branch is `m
4545
version: 2.1
4646

4747
jobs:
48-
# build job ommitted for brevity
48+
# build job omitted for brevity
4949
deploy-job:
5050
docker:
5151
- image: <docker-image-name-tag>

docs/guides/modules/deploy/pages/deploy-to-heroku.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ jobs:
8181
- image: <docker-image-name-tag>
8282
steps:
8383
- checkout
84-
# Additional steps ommitted for brevity
84+
# Additional steps omitted for brevity
8585
deploy:
8686
docker:
8787
- image: <docker-image-name-tag>

docs/guides/modules/getting-started/pages/create-an-organization.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ A `github` organization is created when you log in to CircleCI using your _socia
3232

3333
. Navigate to your link:https://app.circleci.com/settings/user[User settings] page.
3434
. Select the **Account Integrations** from the sidebar.
35-
. At the bottom of the page, select the link that reads `Recieved instructions from the CircleCI Support team to authorize a GitHub OAuth app?`.
35+
. At the bottom of the page, select the link that reads `Received instructions from the CircleCI Support team to authorize a GitHub OAuth app?`.
3636
. Follow the instructions to create a `github` organization.
3737

3838
Once your `github` organization is created you can start setting up and following projects:

docs/guides/modules/getting-started/pages/getting-started.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ To access a job's build environment for troubleshooting, rerun the job with SSH
182182
image:guides:ROOT:getting-started-guide-exp/validate-config.png[float=right]
183183
[%hardbreaks]
184184
*VS Code extension*
185-
Using the xref:toolkit:vs-code-extension-overview.adoc[CircleCI VS Code extention], validate your CircleCI config file. Get help with troubleshooting config updates and help keeping dependencies up to date.
185+
Using the xref:toolkit:vs-code-extension-overview.adoc[CircleCI VS Code extension], validate your CircleCI config file. Get help with troubleshooting config updates and help keeping dependencies up to date.
186186

187187
{empty} +
188188

docs/guides/modules/optimize/pages/optimizations.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ NOTE: Open a link:https://support.circleci.com/hc/en-us/requests/new[Support tic
173173

174174
* Read more about resource classes on the xref:execution-managed:resource-class-overview.adoc[resource class overview] page.
175175
176-
[#configuraiton]
176+
[#configuration]
177177
== Optimize your configuration files
178178

179179
[#dynamic-configuration]

docs/guides/modules/orchestrate/pages/controlling-serial-execution-across-your-organization.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
= Controlling serial execution across your organization
22
:page-platform: Cloud, Server v4.9+
3-
:page-description: An overview of controlloing serial execution accross a CircleCI org.
3+
:page-description: An overview of controlling serial execution across a CircleCI org.
44
:experimental:
55

66
Serial groups enable controlled, sequential execution of CircleCI jobs across your organization to prevent conflicts when multiple jobs need to access shared resources or when operation order is critical.

docs/guides/modules/permissions-authentication/pages/users-organizations-and-integrations-guide.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ For `circleci` type organizations, projects are created directly in CircleCI via
140140

141141
=== Organization integration
142142

143-
The organizaiton integration options available to you depend on your organization type. By _integration_ here we mean the way CircleCI checks out your code from your VCS provider. Options are as follows:
143+
The organization integration options available to you depend on your organization type. By _integration_ here we mean the way CircleCI checks out your code from your VCS provider. Options are as follows:
144144

145145
[.table-scroll]
146146
--
@@ -187,7 +187,7 @@ The following limits are currently in place for the Free Plan:
187187
- Each user can create up to three `circleci` organizations on the Free Plan.
188188
- Each `circleci` organization under a Free Plan can have up to 10 projects.
189189

190-
If you need more organizations or projects, consider upgrading to a Paid Plan or link:https://support.circleci.com/hc/en-us/requests/new[contact our Support team]. See hte xref:plans-pricing:plan-overview.adoc[Plan Overview] page for more information.
190+
If you need more organizations or projects, consider upgrading to a Paid Plan or link:https://support.circleci.com/hc/en-us/requests/new[contact our Support team]. See the xref:plans-pricing:plan-overview.adoc[Plan Overview] page for more information.
191191

192192
== Quickstart
193193

0 commit comments

Comments
 (0)