Remove KOTS existing cluster UI-based tutorial

docs/enterprise/installing-existing-cluster-automation.mdx

@@ -41,7 +41,7 @@ One common use case for installing with the CLI is to automate installation, suc
 
 For more information about the advanced options for the `kots install` command, see [install](/reference/kots-cli-install) in the KOTS CLI documentation.
 
-For a tutorial that demonstrates how to install a sample application using the KOTS CLI, see [KOTS Tutorial (CLI)](/vendor/tutorial-cli-setup).
+For a tutorial that demonstrates how to install a sample application using the KOTS CLI, see [Install with KOTS in an Existing Cluster](/vendor/tutorial-cli-setup).
 
 ## Limitation
 

docs/vendor/distributing-workflow.md

@@ -17,7 +17,7 @@ If you are new to Replicated, complete the following prerequisites before you ge
      Packaging your application with Helm is recommended because it allows you to support both installations with the Helm CLI and with KOTS from the same release, without having to maintain separate sets of Helm charts or application manifests.
      :::
 
-  * Alternatively, if you do _not_ intend to distribute a Helm chart-based application with Replicated, see [KOTS Tutorial (UI)](tutorial-ui-setup) for a workflow that uses a sample application with standard Kubernetes manifests.
+  * Alternatively, if you do _not_ intend to distribute a Helm application with Replicated, see [Install with KOTS in an Existing Cluster](tutorial-cli-setup) for a workflow that uses a sample application with Kubernetes manifests.
 
 ## Add Custom Resources
 

docs/vendor/helm-native-about.mdx

@@ -36,7 +36,7 @@ Additionally, for applications packaged as Helm charts, you can support Helm CLI
 
 [View a larger version of this image](/images/helm-kots-install-options.png)
 
-For a tutorial that demonstrates how to add a sample Helm chart to a release and then install the release using both KOTS and the Helm CLI, see [Deploy a Helm Chart with KOTS and the Helm CLI](/vendor/tutorial-kots-helm-setup).
+For a tutorial that demonstrates how to add a sample Helm chart to a release and then install the release using both KOTS and the Helm CLI, see [Install a Helm Chart with KOTS and the Helm CLI](/vendor/tutorial-kots-helm-setup).
 
 ## How KOTS Deploys Helm Charts
 

docs/vendor/kots-faq.mdx

@@ -95,7 +95,7 @@ The UI-based installation experience of KOTS can provide an easier installation
 
 Yes. Software vendors that distribute their application as one or more Helm charts can support installations with both the Helm CLI and with KOTS from the same release.
 
-For a tutorial that demonstrates how to add the Bitnami Gitea Helm chart to a release in the Replicated Vendor Portal and then install with both KOTS and the Helm CLI, see [Deploy a Helm Chart with KOTS and Helm CLI](/vendor/tutorial-kots-helm-setup).
+For a tutorial that demonstrates how to add the Bitnami Gitea Helm chart to a release in the Replicated Vendor Portal and then install with both KOTS and the Helm CLI, see [Install a Helm Chart with KOTS and Helm CLI](/vendor/tutorial-kots-helm-setup).
 
 ### How does the Replicated SDK work with KOTS?
 

docs/vendor/replicated-onboarding.mdx

@@ -63,7 +63,7 @@ Before you begin, complete the following prerequisites:
        ``` 
 
   :::note
-  If you do not intend to distribute a Helm chart-based application with Replicated, see [KOTS Tutorial (UI)](tutorial-ui-setup) to follow an onboarding workflow that uses a sample application with standard Kubernetes manifests and demonstrates installing with Replicated KOTS.
+  If you do not intend to distribute a Helm application with Replicated, see [Install with KOTS in an Existing Cluster](tutorial-cli-setup) to follow an onboarding workflow that uses a sample application with Kubernetes manifests and demonstrates installing with Replicated KOTS.
   ::: 
 
 * You must have kubectl access to a cluster where you can develop against the Helm chart. Replicated recommends that you confirm that you can successfully install the chart in the cluster and also log in to the application UI. After you confirm that you can install and access the application, uninstall it before proceeding to the onboarding workflow. For more information, see [Helm Install](https://helm.sh/docs/helm/helm_install/) and [Helm Uninstall](https://helm.sh/docs/helm/helm_uninstall/) in the Helm documentation.

docs/vendor/tutorial-adding-db-config.md

@@ -16,9 +16,7 @@ It is split into 5 sections:
 
 This guide assumes you have:
 
-* A running instance of the Replicated Admin Console (`kotsadm`) to iterate against in either an existing cluster or an embedded cluster created with Replicated kURL. If you do not have a running instance of the Admin Console in an existing or embedded kURL cluster, complete one of the following getting started tutorials to package and install a sample application:
-   * [UI Tutorial](tutorial-ui-setup)
-   * [CLI Tutorial](tutorial-cli-setup)
+* A running instance of the Replicated Admin Console (`kotsadm`) to iterate against in either an existing cluster or an embedded cluster created with Replicated kURL. If you do not have a running instance of the Admin Console in an existing or embedded kURL cluster, complete the [Install with KOTS in an Existing Cluster](tutorial-cli-setup) tutorial to package and install a sample application.
 * A local git checkout of your application manifests.
 
 ### Accompanying Code Examples

docs/vendor/tutorial-ci-cd-integration.md

@@ -8,7 +8,7 @@ For a similar workflow that uses GitHub Actions, see [Replicated Kubernetes Star
 
 ## Environment Variables
 
-This section will assume you already have the App slug and API token from the [CLI Tutorial](tutorial-cli-setup).
+This section will assume you already have the App slug and API token from the [Install with KOTS in an Existing Cluster](tutorial-cli-setup) tutorial.
 
 - Configure the following 2 environment variables in your CI/CD configuration.
 

docs/vendor/tutorial-cli-install-cli.mdx

@@ -1,6 +1,6 @@
 # Step 1: Install the Replicated CLI
 
-In this tutorial, you use the Replicated CLI to create and promote releases for a sample application with Replicated. The Replicated CLI is the CLI for the Replicated Vendor Portal. For a tutorial that uses the Replicated Vendor Portal UI to create and promote releases, see [UI Tutorial](tutorial-ui-setup).
+In this tutorial, you use the Replicated CLI to create and promote releases for a sample application with Replicated. The Replicated CLI is the CLI for the Replicated Vendor Portal.
 
 This procedure describes how to create a Vendor Portal account, install the Replicated CLI on your local machine, and set up a `REPLICATED_API_TOKEN` environment variable for authentication.
 

docs/vendor/tutorial-cli-setup.mdx

@@ -10,8 +10,6 @@ import VMRequirements from "../partials/getting-started/_vm-requirements.mdx"
 
 The steps in this KOTS CLI-based tutorial show you how to use the Replicated CLI to perform these tasks. The Replicated CLI is the CLI for the Replicated Vendor Portal. You can use the Replicated CLI as a software vendor to programmatically create, configure, and manage your application artifacts, including application releases, release channels, customer entitlements, private image registries, and more.
 
-For a tutorial that demonstrates how to use the Vendor Portal to create and promote releases for your application, see [UI Tutorial](tutorial-ui-setup).
-
 <KubernetesTraining/>
 
 ## Set Up the Environment

docs/vendor/tutorial-ecr-private-images.md

@@ -38,10 +38,6 @@ We are going to use the default NGINX deployment to create our application and t
 
 In this section, we cover at a high level the steps to create a new application and install it on a VM.
 
-For more detailed information about how to create and install an application, follow one of the following getting started tutorials:
-* [UI Tutorial](tutorial-ui-setup)
-* [CLI Tutorial](tutorial-cli-setup)
-
 To create our sample application follow these steps:
 
 * Create a new application in the Replicated [vendor portal](https://vendor.replicated.com) and call it 'MySampleECRApp'.