diff --git a/applicationset/generators/interface.go b/applicationset/generators/interface.go index 94a6b05577049..578eaf96dd1d3 100644 --- a/applicationset/generators/interface.go +++ b/applicationset/generators/interface.go @@ -14,7 +14,7 @@ type Generator interface { // against the current state of the Applications in the cluster. GenerateParams(appSetGenerator *argoprojiov1alpha1.ApplicationSetGenerator, applicationSetInfo *argoprojiov1alpha1.ApplicationSet) ([]map[string]interface{}, error) - // GetRequeueAfter is the the generator can controller the next reconciled loop + // GetRequeueAfter is the generator can controller the next reconciled loop // In case there is more then one generator the time will be the minimum of the times. // In case NoRequeueAfter is empty, it will be ignored GetRequeueAfter(appSetGenerator *argoprojiov1alpha1.ApplicationSetGenerator) time.Duration diff --git a/applicationset/utils/utils.go b/applicationset/utils/utils.go index b8eda72c38871..b929e5ee0fbc4 100644 --- a/applicationset/utils/utils.go +++ b/applicationset/utils/utils.go @@ -137,7 +137,7 @@ func (r *Render) deeplyReplace(copy, original reflect.Value, replaceMap map[stri copy.SetMapIndex(key, copyValue) } - // Otherwise we cannot traverse anywhere so this finishes the the recursion + // Otherwise we cannot traverse anywhere so this finishes the recursion // If it is a string translate it (yay finally we're doing what we came for) case reflect.String: strToTemplate := original.String() diff --git a/docs/operator-manual/applicationset/Generators-Cluster.md b/docs/operator-manual/applicationset/Generators-Cluster.md index 04546278a7c39..26a457e5de408 100644 --- a/docs/operator-manual/applicationset/Generators-Cluster.md +++ b/docs/operator-manual/applicationset/Generators-Cluster.md @@ -112,7 +112,7 @@ However, if you do wish to target both local and non-local clusters, while also 1. Within the Argo CD web UI, select *Settings*, then *Clusters*. 2. Select your local cluster, usually named `in-cluster`. -3. Click the *Edit* button, and change the the *NAME* of the cluster to another value, for example `in-cluster-local`. Any other value here is fine. +3. Click the *Edit* button, and change the *NAME* of the cluster to another value, for example `in-cluster-local`. Any other value here is fine. 4. Leave all other fields unchanged. 5. Click *Save*. @@ -204,4 +204,4 @@ spec: # In this case this is equivalent to just using {{name}} server: '{{values.clusterName}}' namespace: guestbook -``` \ No newline at end of file +``` diff --git a/docs/proposals/multiple-sources-for-applications.md b/docs/proposals/multiple-sources-for-applications.md index da4d2789998ca..d8c517005d1ea 100644 --- a/docs/proposals/multiple-sources-for-applications.md +++ b/docs/proposals/multiple-sources-for-applications.md @@ -184,7 +184,7 @@ As per one of the [comment]((https://github.com/argoproj/argo-cd/issues/2789#iss ``` We have a Helm Chart which is used in 30+ Services and each of them is customized for 3 possible environments. Replicating this Chart 30 times without a centralized Repo looks dirty. Can be a show stopper for the whole migration. -Modifying the Application definition is not an option since the whole goal is to reduce the rights that the CI-solution has. Giving it the right to update all Application-definitions from various teams in the argocd namespace is a a hard thing to convince people with. +Modifying the Application definition is not an option since the whole goal is to reduce the rights that the CI-solution has. Giving it the right to update all Application-definitions from various teams in the argocd namespace is a hard thing to convince people with. ``` ### Implementation Details diff --git a/docs/user-guide/parameters.md b/docs/user-guide/parameters.md index 83d5b6b49f43d..c66c9ca1bbe40 100644 --- a/docs/user-guide/parameters.md +++ b/docs/user-guide/parameters.md @@ -46,7 +46,7 @@ would result in the application being redeployed with the new image. Since commit access to the repository is unavailable, it is useful to be able to install charts from the public repository and customize the deployment with different parameters, without resorting to forking the repository to make the changes. For example, to install Redis from the Helm chart -repository and customize the the database password, you would run: +repository and customize the database password, you would run: ```bash argocd app create redis --repo https://github.com/helm/charts.git --path stable/redis --dest-server https://kubernetes.default.svc --dest-namespace default -p password=abc123 @@ -91,4 +91,4 @@ where `` is the name of the application the overrides are valid for. If there exists an non-application specific `.argocd-source.yaml`, parameters included in that file will be merged first, and then the application specific parameters are merged, which can also contain overrides to the parameters -stored in the non-application specific file. \ No newline at end of file +stored in the non-application specific file. diff --git a/docs/user-guide/resource_hooks.md b/docs/user-guide/resource_hooks.md index 489a876cd5744..9f8f98e033a20 100644 --- a/docs/user-guide/resource_hooks.md +++ b/docs/user-guide/resource_hooks.md @@ -86,7 +86,7 @@ OutOfSync even though the Job or Workflow was deleted after completion. ## Using A Hook To Send A Slack Message -The following example uses the Slack API to send a a Slack message when sync completes or fails: +The following example uses the Slack API to send a Slack message when sync completes or fails: ```yaml apiVersion: batch/v1 diff --git a/server/server.go b/server/server.go index 6ad19d05a7a65..2d5a36fb717b0 100644 --- a/server/server.go +++ b/server/server.go @@ -967,7 +967,7 @@ func (a *ArgoCDServer) serveExtensions(extensionsSharedPath string, w http.Respo } } -// registerDexHandlers will register dex HTTP handlers, creating the the OAuth client app +// registerDexHandlers will register dex HTTP handlers, creating the OAuth client app func (a *ArgoCDServer) registerDexHandlers(mux *http.ServeMux) { if !a.settings.IsSSOConfigured() { return