Skip to content

Commit 468f277

Browse files
authored
fix(docs): minor spelling corrections (#543)
1 parent 9c81a03 commit 468f277

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

src/understanding-workflow/components.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ For Buildpack-based deploys, the builder component will launch a one-shot Pod
5050
in the `deis` namespace. This pod runs `slugbuilder` component which handles
5151
default and custom buildpacks (specified by `BUILDPACK_URL`). The "compiled"
5252
application results in a slug, consisting of your application code and all of
53-
its depdencies as determined by the buildpack. The slug is pushed to the
53+
its dependencies as determined by the buildpack. The slug is pushed to the
5454
cluster-configured object storage for later execution. For more information
5555
about buildpacks see [using buildpacks][using-buildpacks].
5656

@@ -85,7 +85,7 @@ we highly recommend that you configure [off-cluster object storage][configure-ob
8585
To facilitate experimentation, development and test environments, the default charts for
8686
Workflow include on-cluster object storage via [minio](https://github.com/minio/minio).
8787

88-
If you also feel comforatable using Kubernetes persistent volumes you may
88+
If you also feel comfortable using Kubernetes persistent volumes you may
8989
configure minio to use persistent storage available in your environment.
9090

9191
## Registry
@@ -94,7 +94,7 @@ configure minio to use persistent storage available in your environment.
9494

9595
The registry component is a managed docker registry which holds application
9696
images generated from the builder component. Registry persists the Docker image
97-
iamges to either local storage (in development mode) or to object storage
97+
images to either local storage (in development mode) or to object storage
9898
configured for the cluster.
9999

100100
## Router
@@ -113,7 +113,7 @@ configuration view the router [project documentation][router-documentation].
113113

114114
## Logger: fluentd, logger
115115

116-
The logging subystem consists of two compoents. Fluentd handles log shipping
116+
The logging subsystem consists of two components. Fluentd handles log shipping
117117
and logger maintains a ring-buffer of application logs.
118118

119119

@@ -126,7 +126,7 @@ fluentd ships logs to the logger component, which powers `deis logs`.
126126

127127
**Project Location:** [deis/logger](https://github.com/deis/logger)
128128

129-
The `logger` compoent receives log streams from `fluentd`, collating by
129+
The `logger` component receives log streams from `fluentd`, collating by
130130
Application name. Logger does not persist logs to disk, instead maintaining an
131131
in-memory ring buffer. For more information on logger see the [project
132132
documentation][logger-documentation].

0 commit comments

Comments
 (0)