Merge pull request #3926 from replicatedhq/update-platform-overview

update replicated platform intro

Author: paigecalvert

docs/intro-replicated.mdx

@@ -1,20 +1,25 @@
 # Check entitlements in preflights with Replicated template functions
 
-This topic describes how to check custom entitlements before installation or upgrade using preflight checks and Replicated template functions in the License context. The information in this topic applies to applications installed with KOTS.
+This topic describes how to check custom entitlements before installation or upgrade using preflight checks and Replicated template functions in the License context. The information in this topic applies to applications installed with a Replicated installer (Embedded Cluster, KOTS, kURL).
 
 ## Overview
 
-KOTS includes default logic to control access to features in the Replicated Admin Console and KOTS CLI based on the values for the built-in fields in the customer's license. For example, by default, KOTS uses the built-in `expires_at` field to prevent an instance from receiving updates when the customer license expires. You can add custom logic to your application to control the behavior of your application based on the built-in fields or any of the custom fields that you create.
+The Replicated installers include default logic to control the user experience based on the customer's built-in license fields.
+For example, by default, the Replicated installers use the built-in `expires_at` field to prevent an instance from receiving updates when the customer license expires.
+You can also add custom logic to your application to control the behavior of your application based on the built-in fields or any of the custom fields that you create.
 
-For more information, see [Manage Customer License Fields](licenses-adding-custom-fields). For the list of built-in fields in customer licenses, see [Built-In License Fields](/vendor/licenses-using-builtin-fields).
+For more information, see [Manage Customer License Fields](licenses-adding-custom-fields).
+For the list of built-in fields in customer licenses, see [Built-In License Fields](/vendor/licenses-using-builtin-fields).
 
 ## Add preflights to check entitlements before installation or upgrade {#install}
 
 To enforce entitlements when your customer installs or updates your application,
-you can use the Replicated LicenseFieldValue template function in your application to read the value of license fields. The LicenseFieldValue template function accepts the built-in license fields and any custom fields that you configure. For more information, see [LicenseFieldValue](/reference/template-functions-license-context#licensefieldvalue) in _License Context_.
+you can use the Replicated LicenseFieldValue template function in your application to read the value of license fields.
+The LicenseFieldValue template function accepts the built-in license fields and any custom fields that you configure.
+For more information, see [LicenseFieldValue](/reference/template-functions-license-context#licensefieldvalue) in _License Context_.
 
-For example, a license might limit how many nodes are permitted in a customer's
-cluster. You could define this limit by creating a `node_count` custom license field:
+For example, a license might limit how many nodes are permitted in a customer's cluster.
+You could define this limit by creating a `node_count` custom license field:
 
 | Name | Key | Type | Description |
 |------|-----|------|-------------|
@@ -40,7 +45,8 @@ spec:
               message: The number of nodes matches your license ({{repl LicenseFieldValue "node_count"}})
 ```
 
-In the example above, the preflight check uses the `nodeResources` analyzer and the value of the custom `node_count` field to determine if the customer has exceeded the maximum number of nodes permitted by their license. If the preflight checks fails, a failure message is displayed to the user and KOTS prevents the installation or upgrade from continuing.
+In the example above, the preflight check uses the `nodeResources` analyzer and the value of the custom `node_count` field to determine if the customer has exceeded the maximum number of nodes permitted by their license.
+If the preflight checks fails, a failure message is displayed to the user and KOTS prevents the installation or upgrade from continuing.
 
 For more information about this example, see [How Can I Use License Custom Fields Value in a Pre-Flight Check?](https://help.replicated.com/community/t/how-can-i-use-license-custom-fields-value-in-a-pre-flight-check/624) in Replicated Community.
 

docs/partials/getting-started/_csdl-overview.mdx

@@ -11,11 +11,13 @@ import Requirements from "../partials/embedded-cluster/v2/_requirements.mdx"
 
 # Replicated quick start
 
-This topic provides a quick start workflow to help new users learn about the Replicated Platform. Complete this quick start before you onboard your application to the platform.
+This topic provides a quick start workflow to help new users learn about the Replicated Platform.
+Complete this quick start before you onboard your application to the platform.
 
 ## Introduction
 
-This quick start demonstrates how to create, install, and update releases for a sample Helm chart in the Replicated Platform. You will repeat these same basic steps to create and test releases throughout the onboarding process to integrate Replicated features with your own application.
+This quick start demonstrates how to create, install, and update releases for a sample Helm chart in the Replicated Platform.
+You will repeat these same basic steps to create and test releases throughout the onboarding process to integrate Replicated features with your own application.
 
 The goals of this quick start are to introduce new Replicated users to the following common tasks for the purpose of preparing to onboard to the Replicated Platform:
 
@@ -25,7 +27,7 @@ The goals of this quick start are to introduce new Replicated users to the follo
 
 * Working with the Replicated CLI
 
-* Installing and updating applications on a VM with Replicated Embedded Cluster through the Replicated Admin Console UI.
+* Installing and updating applications on a VM with Replicated Embedded Cluster v2 through the Replicated Admin Console UI.
 
 Replicated recommends that you allow one to two hours to complete this quick start. No prior knowledge of Replicated, Helm, or interacting with the command line is required. However, if you are unfamiliar with these tools, you might allow more time. If you have any questions or need help, don't hesitate to reach out to our team at https://www.replicated.com/contact.
 
@@ -35,7 +37,7 @@ Before you begin, do the following to set up your environment:
 
 * Install the Helm CLI, which is the tool for interacting with Helm and managing Helm charts. See [Install Helm](/vendor/environment-setup#install-helm).
 
-* Ensure that you have access to a VM that meets the requirements for Embedded Cluster:
+* Ensure that you have access to a VM that meets the requirements for Embedded Cluster v2:
 
    * **Option 1: Use Compatibility Matrix.** To use Replicated Compatibility Matrix (CMX) to create a VM, do the following before proceeding: