Remove Helm-only release content

Author: paigecalvert

docs/vendor/releases-about.mdx

@@ -63,44 +63,18 @@ The following describes each of the channel settings:
 
 This section provides additional information about releases, including details about release promotion, properties, sequencing, and versioning.
 
-### Release Types
+### Release Files
 
-You can create the following types of releases in the Vendor Portal:
+A release contains your application files as well as the manifests required to install the application with Replicated KOTS and Replicated Embedded Cluster. 
 
-* **Helm-only Releases**: A release that contains one or more Helm charts. Helm-only releases can be installed with the Helm CLI only. For more information, see [Installing with Helm](install-with-helm).
-
-* **KOTS Releases**: A release that contains your application files as well as the manifests required to install the application with Replicated KOTS. The application files in KOTS releases can be Helm charts and/or Kubernetes manifests. KOTS releases that contain one or more Helm charts can be installed with KOTS or the Helm CLI. For more information, see [Introduction to KOTS](../intro-kots).
-
-The following shows the Helm-only and KOTS release options that appear in the **Create release** dropdown in the Vendor Portal:
-
-<img alt="create a release dropdown" src="/images/create-release-dropdown.png" width="450px"/>
-
-[View a larger version of this image](/images/create-release-dropdown.png)
+The application files in KOTS releases can be Helm charts and/or Kubernetes manifests. KOTS releases that contain one or more Helm charts can be installed with KOTS or the Helm CLI. For more information, see [Introduction to KOTS](../intro-kots).
 
 ### Promotion
 
 Each release is promoted to one or more channels. While you are developing and testing releases, Replicated recommends promoting to a channel that does not have any real customers assigned, such as the default Unstable channel. When the release is ready to be shared externally with customers, you can then promote to a channel that has the target customers assigned, such as the Beta or Stable channel.
 
 A release cannot be edited after it is promoted to a channel. This means that you can test a release on an internal development channel, and know with confidence that the same release will be available to your customers when you promote it to a channel where real customers are assigned.
 
-#### Promoting KOTS-Only and Helm CLI-Only Releases {#kots-helm-releases}
-
-<KotsEntitlement/>
-
-To prevent KOTS or Helm CLI-only customers from accessing a release that they cannot install, Replicated enforces the following release promotion rules:
-
-* A release must contain the required KOTS manifests to be promoted to a channel where one or more KOTS customers are assigned.
-
-  <img width="400px" alt="Release without the required manifests blocked from promotion" src="/images/release-promotion-kots-customers.png"/>
-  
-  [View a larger version of this image](/images/release-promotion-kots-customers.png)
-
-* A release must contain at least one Helm chart to be promoted to a channel where one or more Helm CLI-only customers are assigned.
-
-  <img width="400px" src="/images/release-promotion-helm-customers.png" alt="Release with no helm charts blocked from being promoted"/>
-  
-  [View a larger version of this image](/images/release-promotion-helm-customers.png)
-
 ### Properties
 
 Each release has properties. You define release properties when you promote a release to a channel. You can edit release properties at any time from the channel **Release History** page in the Vendor Portal. For more information, see [Edit Release Properties](releases-creating-releases#edit-release-properties) in _Managing Releases with the Vendor Portal_.

docs/vendor/releases-creating-releases.mdx

@@ -21,22 +21,9 @@ To create and promote a release in the Vendor Portal:
 
    [View a larger version of this image](/images/release-create-new.png)
 
-1. If a drop down is displayed, select one of the following options:
-   * **Create Helm-only release**: Create a release with one or more Helm charts. Supports installations with the Helm CLI only.
-   * **Create KOTS release**: Create a release that supports installations with Replicated KOTS. KOTS releases can contain Kubernetes manifests and one or more Helm charts. KOTS releases that contain Helm charts can also be installed with the Helm CLI.
-
-   If no drop down is displayed, continue to the next step.  
-
-1. Add your files to the release:
-   * **Helm-only**: For Helm-only releases, follow the steps in the **Add the Replicated SDK to your Helm Chart**  dialog to package your chart and upload a `.tgz` chart archive.
-   
-     <img src="/images/upload-helm-chart-modal.png" alt="upload helm chart dialog" width="550px"/>
-
-     [View a larger version of this image](/images/upload-helm-chart-modal.png)
-
-   * **KOTS**: For KOTS releases, drag and drop your release files to the file directory in the YAML editor. You can also click the plus icon to add a new, untitled YAML file.
+1. Add your files to the release. You can do this by dragging and dropping files to the file directory in the YAML editor or clicking the plus icon to add a new, untitled YAML file.
 
-     For any Helm charts that you add, in the **Select Installation Method** dialog, select the version of the HelmChart custom resource that KOTS will use to install the chart. kots.io/v1beta2 is recommended. For more information about the HelmChart custom resource, see [Configuring the HelmChart Custom Resource](helm-native-v2-using).
+1. For any Helm charts that you add to the release, in the **Select Installation Method** dialog, select the version of the HelmChart custom resource that KOTS will use to install the chart. kots.io/v1beta2 is recommended. For more information about the HelmChart custom resource, see [Configuring the HelmChart Custom Resource](helm-native-v2-using).
 
      <img src="/images/helm-select-install-method.png" alt="select installation method dialog" width="550px"/>