Skip to content

Commit deab5b3

Browse files
yukinakanakajessebye
authored andcommitted
docs: Fixed typo (argoproj-labs#589)
Signed-off-by: Jesse Bye <8467862+jessebye@users.noreply.github.com>
1 parent 36f185b commit deab5b3

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

docs/basics/authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Authentication in Argo CD Image Updater
22

33
There are several scenarios where Argo CD Image Updater needs to authenticate
4-
to external systems in order to fulfil its duties.
4+
to external systems in order to fulfill its duties.
55

66
## <a name="auth-kubernetes"></a>Authentication to Kubernetes
77

@@ -207,7 +207,7 @@ echo "someuser:s0mep4ssw0rd"
207207

208208
When executing on Kubernetes, the script to be executed must exist in the
209209
Image Updater container's file system. You can either mount the script from
210-
a config map, or use an init container to copy it. Make sure that the script
210+
a configmap, or use an init container to copy it. Make sure that the script
211211
is executable.
212212

213213
For example, if above script would exist at `/usr/local/bin/creds.sh`, it

docs/basics/update-methods.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
## Overview
44

55
Argo CD Image Updater supports several methods to propagate new versions of the
6-
images to Argo CD. These methods are also refered to as *write back methods*.
6+
images to Argo CD. These methods are also referred to as *write back methods*.
77

88
Currently, the following methods are supported:
99

@@ -162,7 +162,7 @@ argocd-image-updater.argoproj.io/git-branch: main
162162

163163
### <a name="method-git-base-commit-branch"></a>Specifying a separate base and commit branch
164164

165-
By default, Argo CD Imager Updater will checkout, commit, and push back to the
165+
By default, Argo CD Image Updater will checkout, commit, and push back to the
166166
same branch specified above. There are many scenarios where this is not
167167
desired or possible, such as when the default branch is protected. You can
168168
add a separate write-branch by modifying `argocd-image-updater.argoproj.io/git-branch`

docs/basics/update.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ The workflow of Argo CD Image Updater can be described as follows:
1818
annotation holds a list of image names that should be updated, and is a
1919
mandatory annotation for Argo CD Image Updater to indicate it should
2020
process this `Application`. Read more about the syntax expected in this
21-
annotations's value in the [marking images for update](#TODO)
21+
annotation's value in the [marking images for update](#TODO)
2222
section in this doc.
2323

2424
* For each image found in the list, Argo CD Image Updater will first check

docs/install/reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ Only process applications that have a valid annotation and match the given
123123
syntax of `key=value`. For e.g, `custom.label/name=xyz` would be a valid label
124124
that can be supplied through this parameter. Any applications carrying this
125125
exact label will be considered as candidates for image updates. This parameter
126-
currently does not support patten matching on label values (e.g `customer.label/name=*-staging`)
126+
currently does not support pattern matching on label values (e.g `customer.label/name=*-staging`)
127127
and only accepts a single label to match applications against.
128128

129129
**--max-concurrency *number* **

0 commit comments

Comments
 (0)