From d8c7fd3d69492ef69ba3cda7490c10e6727974d4 Mon Sep 17 00:00:00 2001
From: Jerry Jones <28451941+stratusjerry@users.noreply.github.com>
Date: Tue, 11 Jun 2024 22:39:43 +0000
Subject: [PATCH] typo fixes

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 0f9454e..55dcfbb 100644
--- a/README.md
+++ b/README.md
@@ -24,7 +24,7 @@ both explicitly (see `HELMFILE_INIT_SCRIPT_FILE` env below) and implicity.
 
 Consider these implications for your environment and act appropriately.
 
-- https://github.com/roboll/helmfile#templating (`exec` desciption)
+- https://github.com/roboll/helmfile#templating (`exec` description)
 - https://github.com/helmfile/helmfile/pull/1 (can disable `exec` using env vars)
 - the execution pod/context is the `argocd-repo-server`
 
@@ -112,7 +112,7 @@ repoServer:
 # Usage
 
 Configure your `argo-cd` app to use a repo/directory which holds a valid
-`helmfile` configuation. This can be a directory which contains a
+`helmfile` configuration. This can be a directory which contains a
 `helmfile.yaml` file **OR** a `helmfile.d` directory containing any number of
 `*.yaml` files. You cannot have both configurations.
 
@@ -161,7 +161,7 @@ variables declared in the application spec.
 ## Helm Plugins
 
 To use the various helm plugins the recommended approach is the install the
-plugins using the/an `initContainers` (explicity set the `HELM_DATA_HOME` env
+plugins using the/an `initContainers` (explicitly set the `HELM_DATA_HOME` env
 var during the `helm plugin add` command) and simply set the `HELM_DATA_HOME`
 environment variable in your application spec (or globally in the pod). This
 prevents the plugin(s) from being downloaded over and over each run.