merged and tidied

Author: rain-on

src/pages/docs/argo-cd/steps/deployment-preview/index.md

@@ -3,7 +3,7 @@ layout: src/layouts/Default.astro
 pubDate: 2025-09-15
 modDate: 2025-09-15
 title: Argo CD Deployment Preview
-description: Query affected applications before triggering the chanbge
+description: Query affected applications before triggering the change
 ---
 Argo CD Instances don't fall under the category of 'Deployment Target', and so 'Target Tags' can't be used by the associated
 steps to specify which Argo application is to be updated by a given deployment.

src/pages/docs/argo-cd/steps/index.md

@@ -16,7 +16,7 @@ Octopus offers two in-built steps which are able to modify a mapped Argo CD appl
 This step is responsible for identifying images referenced by an application, and updating their image-tags to the
 value defined in the Octopus Deployment.
 
-For 'Basic Yaml' and 'Kustomize' based Argo CD Applications, the behaviour for performing the update relies on the known
+For 'Basic Yaml' and 'Kustomize' based Argo CD Applications, the behavior for performing the update relies on the known
 structure of the kubernetes/kustomize yaml to ensure the correct fields are updated.
 
 However, for Helm-based Argo CD Applications, where image-tags are specified within the `values.yaml` file, additional