minor edit

paigecalvert · paigecalvert · commit 624a8b2effc4 · 2025-01-27T14:51:20.000-07:00
diff --git a/docs/release-notes/rn-app-manager.md b/docs/release-notes/rn-app-manager.md
@@ -40,7 +40,7 @@ Support for Kubernetes: 1.29, 1.30, and 1.31
 
    This flag allows Helm to take ownership of existing resources that were installed without Helm, like resources deployed with HelmChart v1beta1 and `useHelmInstall: false`.
 
-   To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or email.
+   To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or over email.
 
 ## 1.123.1
 
diff --git a/docs/vendor/helm-native-v2-using.md b/docs/vendor/helm-native-v2-using.md
@@ -366,4 +366,4 @@ The `kots.io/v1beta2` HelmChart custom resource has the following differences fr
 
 After you complete the tasks in this topic to configure the `kots.io/v1beta2` HelmChart custom resource, you can migrate any existing installations that were deployed with `kots.io/v1beta1` with `useHelmInstall: true` to use `kots.io/v1beta2` instead. For more information, see [Migrating Existing Installations to HelmChart v2](helm-v2-migrate).
 
-To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or email.
+To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or over email.
diff --git a/docs/vendor/helm-v2-migrate.md b/docs/vendor/helm-v2-migrate.md
@@ -8,7 +8,7 @@ The HelmChart custom resource `kots.io/v1beta1` is deprecated and is not recomme
 
 ### `useHelmInstall: false` Limitation
 
-To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or email.
+To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or over email.
 
 ## How to Migrate Existing Installations
 

Original file line number	Diff line number	Diff line change
@@ -366,4 +366,4 @@ The `kots.io/v1beta2` HelmChart custom resource has the following differences fr
`366`	`366`
`367`	`367`	After you complete the tasks in this topic to configure the `kots.io/v1beta2` HelmChart custom resource, you can migrate any existing installations that were deployed with `kots.io/v1beta1` with `useHelmInstall: true` to use `kots.io/v1beta2` instead. For more information, see [Migrating Existing Installations to HelmChart v2](helm-v2-migrate).
`368`	`368`
`369`		-To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or email.
	`369`	+To migrate an existing installation from `kots.io/v1beta1` with `useHelmInstall: false` to `kots.io/v1beta2`, reach out to your Replicated Solutions Engineer in Slack or over email.