change Helm CLI to Helm

Author: paigecalvert

docs/vendor/preflight-defining.mdx

@@ -2,25 +2,25 @@
 
 This topic describes how to define preflight checks in Helm and Kubernetes manifest-based applications. For more information about preflight checks, see [About Preflight Checks and Support Bundles](/vendor/preflight-support-bundle-about).
 
-The information in this topic applies to applications that are installed with the Helm CLI or with Replicated KOTS.
+The information in this topic applies to applications that are installed with Helm or with Replicated KOTS.
 
 ## Step 1: Create the Manifest File
 
-You can define preflight checks in a Kubernetes Secret or in a Preflight custom resource. The type of manifest file that you use depends on your application type (Helm or Kubernetes manifest-based) and the installation methods that your application supports (Helm CLI, KOTS v1.101.0 or later, or KOTS v1.100.3 or earlier).
+You can define preflight checks in a Kubernetes Secret or in a Preflight custom resource. The type of manifest file that you use depends on your application type (Helm or Kubernetes manifest-based) and the installation methods that your application supports (Helm, KOTS v1.101.0 or later, or KOTS v1.100.3 or earlier).
 
 * **Helm Applications**: For Helm applications, see the following guidance:
 
-   * **(Recommended) Helm CLI or KOTS v1.101.0 or Later**: For Helm applications installed with the Helm CLI or KOTS v1.101.0 or later, define the preflight checks in a Kubernetes Secret in your Helm chart `templates`. See [Kubernetes Secret](#secret).
+   * **(Recommended) Helm or KOTS v1.101.0 or Later**: For Helm applications installed with Helm or KOTS v1.101.0 or later, define the preflight checks in a Kubernetes Secret in your Helm chart `templates`. See [Kubernetes Secret](#secret).
 
    * **KOTS v1.100.3 or Earlier**: For Helm applications installed with KOTS v1.100.3 or earlier, define the preflight checks in a Preflight custom resource. See [Preflight Custom Resource](#preflight-cr).
 
 * **Kubernetes Manifest-Based Applications**: For Kubernetes manifest-based applications, define the preflight checks in a Preflight custom resource. See [Preflight Custom Resource](#preflight-cr).
 
 ### Kubernetes Secret {#secret}
 
-For Helm applications installed with the Helm CLI or KOTS v1.101.0 or later, define preflight checks in a Kubernetes Secret in your Helm chart `templates`. This allows you to define the preflights spec only one time to support running preflight checks in both Helm CLI and KOTS installations. 
+For Helm applications installed with Helm or KOTS v1.101.0 or later, define preflight checks in a Kubernetes Secret in your Helm chart `templates`. This allows you to define the preflights spec only one time to support running preflight checks in both Helm and KOTS installations. 
 
-For a tutorial that demonstrates how to define preflight checks in a Secret in chart `templates` and then run the preflight checks in both Helm CLI and KOTS installations, see [Tutorial: Add Preflight Checks to a Helm Chart](/vendor/tutorial-preflight-helm-setup).
+For a tutorial that demonstrates how to define preflight checks in a Secret in chart `templates` and then run the preflight checks in both Helm and KOTS installations, see [Tutorial: Add Preflight Checks to a Helm Chart](/vendor/tutorial-preflight-helm-setup).
 
 Add the following YAML to a Kubernetes Secret in your Helm chart `templates` directory:
 

docs/vendor/support-bundle-customizing.mdx

@@ -6,13 +6,13 @@ The information in this topic applies to Helm applications and Kubernetes manife
 
 ## Step 1: Add the Default Spec to a Manifest File
 
-You can add the support bundle spec to a Kubernetes Secret or a SupportBundle custom resource. The type of manifest file that you use depends on your application type (Helm or manifest-based) and installation method (Helm CLI or KOTS).
+You can add the support bundle spec to a Kubernetes Secret or a SupportBundle custom resource. The type of manifest file that you use depends on your application type (Helm or manifest-based) and installation method (Helm or KOTS).
 
 Use the following guidance to determine which type of manifest file to use for creating a support bundle spec:
 
 * **Helm Applications**: For Helm applications, see the following guidance:
 
-   * **(Recommended) Helm CLI or KOTS v1.94.2 and Later**: For Helm applications installed with Helm or KOTS v1.94.2 or later, create the support bundle spec in a Kubernetes Secret in your Helm chart `templates`. See [Kubernetes Secret](#secret).
+   * **(Recommended) Helm or KOTS v1.94.2 and Later**: For Helm applications installed with Helm or KOTS v1.94.2 or later, create the support bundle spec in a Kubernetes Secret in your Helm chart `templates`. See [Kubernetes Secret](#secret).
 
    * **KOTS v1.94.1 and Earlier**: For Helm applications installed with KOTS v1.94.1 or earlier, create the support bundle spec in a Preflight custom resource. See [Preflight Custom Resource](#preflight-cr).
 
@@ -21,7 +21,7 @@ Use the following guidance to determine which type of manifest file to use for c
 ### Kubernetes Secret
 
 You can define support bundle specs in a Kubernetes Secret for the following installation types:
-* Installations with the Helm CLI
+* Installations with Helm
 * Helm applications installed with KOTS v1.94.2 and later
 
 In your Helm chart `templates` directory, add the following YAML to a Kubernetes Secret: