Update license docs to reflect install type options

Author: paigecalvert

docs/vendor/releases-creating-customer.mdx

@@ -8,7 +8,7 @@ This topic describes how to create and manage customers in the Replicated Vendor
 
 ## Create a Customer
 
-This procedure describes how to create a new customer in the Vendor Portal. You can edit customer details at any time in the Vendor Portal.
+This procedure describes how to create a new customer in the Vendor Portal. You can edit customer details at any time.
 
 For information about creating a customer with the Replicated CLI, see [customer create](/reference/replicated-cli-customer-create).
 
@@ -24,56 +24,31 @@ To create a customer:
 
 1. For **Customer name**, enter a name for the customer.
 
-1. For **Customer email**, enter the email address for the customer. The customer email address is required for Helm installations. This email address is never used send emails to customers.
+1. For **Customer email**, enter the email address for the customer.
+
+   :::note
+   A customer email address is required for Helm installations. This email address is never used to send emails to customers.
+   :::
 
 1. For **Assigned channel**, assign the customer to one of your channels. You can select any channel that has at least one release. The channel a customer is assigned to determines the application releases that they can install. For more information, see [Channel Assignment](licenses-about#channel-assignment) in _About Customers_.
 
    :::note
    <ChangeChannel/>
    :::
 
-1. For **Custom ID**, you can enter a custom ID for the customer. Setting a custom ID allows you to easily tie this Replicated customer record to your own internal customer data systems during data exports. We suggest setting an alphanumeric value such as your Salesforce ID, Hubspot ID, etc for that customer. Replicated does not require the custom ID to be unique. The custom ID is for vendor data reconciliation purposes, and is not used by Replicated for any functionality purposes.
+1. For **Custom ID**, you can enter a custom ID for the customer. Setting a custom ID allows you to easily associate this Replicated customer record to your own internal customer data systems during data exports. Replicated recommends using an alphanumeric value such as your Salesforce ID or Hubspot ID.
+
+   :::note
+   Replicated does _not_ require that the custom ID is unique. The custom ID is for vendor data reconciliation purposes, and is not used by Replicated for any functionality purposes.
+   :::
 
 1. For **Expiration policy**, by default, **Customer's license does not expire** is enabled. To set an expiration date for the license, enable **Customer's license has an expiration date** and specify an expiration date in the **When does this customer expire?** calendar. 
 
 1. For **Customer type**, set the customer type. Customer type is used only for reporting purposes. Customer access to your application is not affected by the type you assign to them. By default, **Trial** is selected. For more information, see [About Customer License Types](licenses-about-types).
 
-1. In the **License options** pane, configure any of the built-in KOTS entitlements that you support in your application. For more information, see [Built-in License Fields](licenses-using-builtin-fields).
-
-    The available license options are:
-
-      <table>
-        <tr>
-          <th width="30%">Name</th>
-          <th width="70%">Description</th>
-        </tr>
-        <tr>
-          <td>KOTS Install Enabled</td>
-          <td>Enables customers to install with Replicated KOTS.</td>
-        </tr>
-        <tr>
-          <td>Airgap Download Enabled</td>
-          <td>Enables new installations with this license to install from an air gap package or from an online installation.</td>
-        </tr>
-        <tr>
-          <td>Gitops Enabled</td>
-          <td> <GitOpsNotRecommended/> Enables customers with a KOTS-managed installation to transition from click-to-deploy to the KOTS Auto-GitOps workflow for deployment. See <a href="/enterprise/gitops-workflow">KOTS Auto-GitOps Workflow</a>. </td>
-        </tr>
-        <tr>
-          <td>Identity Service Enabled</td>
-          <td>Enables customers to integrate with third-party identity service providers to provision RBAC for authenticating to the admin console.</td>
-        </tr>
-        <tr>
-          <td>Support Bundle Upload Enabled</td>
-          <td>Enables installations to upload support bundles directly from the admin console.</td>
-        </tr>
-        <tr>
-          <td>Allow Snapshot</td>
-          <td>Enables customers to create snapshots for backup and restore. Vendors must also add a Backup custom resource. See <a href="/reference/custom-resource-backup">Velero Backup Custom Resource</a>.</td>
-        </tr>
-      </table>
-
-1. (Optional) For **Custom fields**, configure any custom fields that are available for your Replicated application. For more information about how to create custom fields for your application, see [Managing Custom License Fields](licenses-adding-custom-fields).
+1. For the built-in license options, enable any of the options that you want to support for the customer. For more information, see [Built-in License Fields](licenses-using-builtin-fields).
+
+1. For **Custom fields**, configure any custom fields that you have added for your application. For more information about how to create custom fields for your application, see [Managing Custom License Fields](licenses-adding-custom-fields).
 
 1. Click **Save Changes**.