Skip to content

docs: Fixed typo #589

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 8, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/basics/authentication.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Authentication in Argo CD Image Updater

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

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

Expand Down Expand Up @@ -207,7 +207,7 @@ echo "someuser:s0mep4ssw0rd"

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

For example, if above script would exist at `/usr/local/bin/creds.sh`, it
Expand Down
4 changes: 2 additions & 2 deletions docs/basics/update-methods.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
## Overview

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

Currently, the following methods are supported:

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

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

By default, Argo CD Imager Updater will checkout, commit, and push back to the
By default, Argo CD Image Updater will checkout, commit, and push back to the
same branch specified above. There are many scenarios where this is not
desired or possible, such as when the default branch is protected. You can
add a separate write-branch by modifying `argocd-image-updater.argoproj.io/git-branch`
Expand Down
2 changes: 1 addition & 1 deletion docs/basics/update.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The workflow of Argo CD Image Updater can be described as follows:
annotation holds a list of image names that should be updated, and is a
mandatory annotation for Argo CD Image Updater to indicate it should
process this `Application`. Read more about the syntax expected in this
annotations's value in the [marking images for update](#TODO)
annotation's value in the [marking images for update](#TODO)
section in this doc.

* For each image found in the list, Argo CD Image Updater will first check
Expand Down
2 changes: 1 addition & 1 deletion docs/install/reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ Only process applications that have a valid annotation and match the given
syntax of `key=value`. For e.g, `custom.label/name=xyz` would be a valid label
that can be supplied through this parameter. Any applications carrying this
exact label will be considered as candidates for image updates. This parameter
currently does not support patten matching on label values (e.g `customer.label/name=*-staging`)
currently does not support pattern matching on label values (e.g `customer.label/name=*-staging`)
and only accepts a single label to match applications against.

**--max-concurrency *number* **
Expand Down