removing embedded kurl language

Author: paigecalvert

docs/enterprise/cluster-management-add-nodes.md

@@ -1,10 +1,10 @@
 # Adding Nodes to kURL Clusters
 
-This topic describes how to add primary and secondary nodes to an embedded cluster provisioned with Replicated kURL.
+This topic describes how to add primary and secondary nodes to a Replicated kURL cluster.
 
 ## Overview
 
-You can generate commands in the Replicated KOTS Admin Console to join additional primary and secondary nodes to embedded kURL clusters. Primary nodes run services that control the cluster. Secondary nodes run services that control the pods that host the application containers. Adding nodes can help manage resources to ensure that the application runs smoothly.
+You can generate commands in the Replicated KOTS Admin Console to join additional primary and secondary nodes to kURL clusters. Primary nodes run services that control the cluster. Secondary nodes run services that control the pods that host the application containers. Adding nodes can help manage resources to ensure that the application runs smoothly.
 
 For high availability clusters, Kubernetes recommends using at least three primary nodes, and that you use an odd number of nodes to help with leader selection if machine or zone failure occurs. For more information, see [Creating Highly Available Clusters with kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/) in the Kubernetes documentation.
 

docs/enterprise/image-registry-kurl.md

@@ -26,7 +26,7 @@ For more information, see [admin-console garbage-collect-images](/reference/kots
 
 ## Disable Image Garbage Collection
 
-Image garbage collection is enabled by default for embedded kURL clusters that use the kURL registry.
+Image garbage collection is enabled by default for kURL clusters that use the kURL registry.
 
 To disable image garbage collection:
 
@@ -56,8 +56,8 @@ The kURL registry image garbage collection feature has following limitations:
 
    To prevent this from happening, include the optional images in the `additionalImages` list of the Application custom resource. For more information, see [`additionalImages`](/reference/custom-resource-application#additionalimages) in _Application_.
 
-* **Shared Image Registries**: The image garbage collection process assumes that the registry is not shared with any other instances of Replicated KOTS, nor shared with any external applications. If the embedded kURL registry is used by another external application, disable garbage collection to prevent image loss.
+* **Shared Image Registries**: The image garbage collection process assumes that the registry is not shared with any other instances of Replicated KOTS, nor shared with any external applications. If the built-in kURL registry is used by another external application, disable garbage collection to prevent image loss.
 
-* **Customer Supplied Registries**: Image garbage collection is supported only when used with the embedded kURL registry. If the KOTS instance is configured to use a different registry, disable garbage collection to prevent image loss.
+* **Customer Supplied Registries**: Image garbage collection is supported only when used with the built-in kURL registry. If the KOTS instance is configured to use a different registry, disable garbage collection to prevent image loss.
 
 * **Application Rollbacks**: Image garbage collection has no effect when the `allowRollback` field in the KOTS Application custom resource is set to `true`. For more information, see [Application](/reference/custom-resource-application) in _KOTS Custom Resources_.

docs/enterprise/installing-stateful-component-requirements.md

@@ -11,22 +11,22 @@ The Replicated KOTS Admin Console requires persistent storage for state. By defa
 
 For more information about the Admin Console's persistent storage requirements, see [Minimum System Requirements](/enterprise/installing-general-requirements#minimum-system-requirements) in _Installation Requirements_.
 
-For existing cluster installations, KOTS deploys MinIO for object storage by default. For embedded cluster installations with Replicated kURL, the object storage provider is either MinIO or Rook, depending on which add-on your software vendor included in the kURL installer specification. 
+For existing cluster installations, KOTS deploys MinIO for object storage by default. For installations with Replicated kURL, the object storage provider is either MinIO or Rook, depending on which add-on your software vendor included in the kURL installer specification. 
 
 You can optionally install KOTS without object storage. When installed without object storage, KOTS deploys the Admin Console as a Statefulset with an attached PersistentVolume (PV) instead of as a deployment. In this case, support bundles and application archives are stored in the attached PV instead of in object storage. Additionally, for local snapshots storage, KOTS uses the `local-volume-provider` Velero plugin to store backups on local PVs instead of using object storage. The `local-volume-provider` plugin uses the existing Velero service account credentials to mount volumes directly to the Velero node-agent pods. For more information, see [`local-volume-provider`](https://github.com/replicatedhq/local-volume-provider) in GitHub.
 
 ## Install Without Object Storage
 
-This section describes how to install KOTS without object storage in existing clusters or embedded kURL clusters.
+This section describes how to install KOTS without object storage in existing clusters or kURL clusters.
 
 ### Existing Clusters
 
 To install KOTS without object storage in an existing cluster, you can use the `--with-minio=false` flag:
 * When `--with-minio=false` is used with the `kots install` command, KOTS does _not_ deploy MinIO. KOTS deploys the Admin Console as a Statefulset with an attached PV instead of as a deployment. For command usage, see [install](/reference/kots-cli-install/).
 * When `--with-minio=false` is used with the `kots admin-console upgrade` command, KOTS upgrades the existing Admin Console instance to the latest version, replaces the running deployment with a StatefulSet, and removes MinIO after a data migration. This results in temporary downtime for the Admin Console, but deployed applications are unaffected. For command usage, see [admin-console upgrade](/reference/kots-cli-admin-console-upgrade/).
 
-### Embedded kURL Clusters
+### kURL Clusters
 
-To enable KOTS installations without object storage in embedded kURL clusters, your software vendor must remove the MinIO or Rook object storage add-on from the kURL installer spec and set the `disableS3` flag to `true` in the KOTS add-on.
+To enable KOTS installations without object storage in kURL clusters, your software vendor must remove the MinIO or Rook object storage add-on from the kURL installer spec and set the `disableS3` flag to `true` in the KOTS add-on.
 
-For more information about the behavior of the `disableS3` flag, see [KOTS Add-on](https://kurl.sh/docs/add-ons/kotsadm) in the open source kURL documentation. For information about migrating an embedded kURL cluster away from object storage, see [Removing Object Storage](https://kurl.sh/docs/install-with-kurl/removing-object-storage) in the kURL documentation.
+For more information about the behavior of the `disableS3` flag, see [KOTS Add-on](https://kurl.sh/docs/add-ons/kotsadm) in the open source kURL documentation. For information about migrating a kURL cluster away from object storage, see [Removing Object Storage](https://kurl.sh/docs/install-with-kurl/removing-object-storage) in the kURL documentation.

docs/enterprise/snapshots-understanding.mdx

@@ -85,7 +85,7 @@ You initially configure backups on a supported storage provider backend using th
 - Network File System (NFS)
 - Host Path
 
-kURL installers that include the Velero add-on also include a locally-provisioned object store. By default, embedded kURL clusters are preconfigured in the Admin Console to store backups in the locally-provisioned object store. This object store is sufficient for only rollbacks and downgrades and is not a suitable configuration for disaster recovery. Replicated recommends that you configure a snapshots storage destination that is external to the cluster in the Admin Console for embedded kURL clusters.
+kURL installers that include the Velero add-on also include a locally-provisioned object store. By default, kURL clusters are preconfigured in the Admin Console to store backups in the locally-provisioned object store. This object store is sufficient for only rollbacks and downgrades and is not a suitable configuration for disaster recovery. Replicated recommends that you configure a snapshots storage destination that is external to the cluster in the Admin Console for kURL clusters.
 
 For information about how to configure backup storage destinations for snapshots, see the [Configuring Backup Storage](/enterprise/snapshots-velero-cli-installing) section.
 

docs/vendor/admin-console-port-forward.mdx

@@ -204,7 +204,7 @@ To test this example:
     <Tabs>
     <TabItem value="service" label="example-service.yaml" default>
     <h5>Description</h5>
-    <p>The YAML below contains ClusterIP and NodePort specifications for a service named <code>nginx</code>. Each specification uses the <code>kots.io/when</code> annotation with the Replicated IsKurl template function to conditionally include the service based on the installation type (existing cluster or embedded kURL cluster). For more information, see <a href="/vendor/packaging-include-resources">Conditionally Including or Excluding Resources</a> and <a href="/reference/template-functions-static-context#iskurl">IsKurl</a>.</p>
+    <p>The YAML below contains ClusterIP and NodePort specifications for a service named <code>nginx</code>. Each specification uses the <code>kots.io/when</code> annotation with the Replicated IsKurl template function to conditionally include the service based on the installation type (existing cluster or kURL cluster). For more information, see <a href="/vendor/packaging-include-resources">Conditionally Including or Excluding Resources</a> and <a href="/reference/template-functions-static-context#iskurl">IsKurl</a>.</p>
     <p>As shown below, both the ClusterIP and NodePort <code>nginx</code> services are exposed on port 80.</p>
     <h5>YAML</h5>
     <NginxService/>

docs/vendor/helm-native-about.mdx

@@ -202,7 +202,7 @@ To deploy Helm charts with version `kots.io/v1beta1` of the HelmChart custom res
     kind: Kustomization
     ```
 
-   End users can edit the downstream Kustomization files to make changes before deploying the application. Any instructions that users add to the Kustomization files in the downstream directory take priority over midstream and base Kustomization files. For more information about how users can make changes before deploying, see [Patching with Kustomize](/enterprise/updating-patching-with-kustomize) in _Enterprise User Documentation_.
+   End users can edit the downstream Kustomization files to make changes before deploying the application. Any instructions that users add to the Kustomization files in the downstream directory take priority over midstream and base Kustomization files. For more information about how users can make changes before deploying, see [Patching with Kustomize](/enterprise/updating-patching-with-kustomize).
 
 1. **Deploys the Helm chart**: KOTS runs `kustomize build` for any Kustomization files in the `overlays/downstream/charts` directory. KOTS then packages the resulting manifests into a new chart for Helm to consume.
 

docs/vendor/packaging-ingress.md

@@ -6,7 +6,7 @@ Below is an example of a flexible `ingress.yaml` file designed to work in most K
 ## Example
 
 The following example includes an Ingress resource with a single host based routing rule.
-The resource works in both existing clusters and embedded kURL clusters.
+The resource works in both existing clusters and kURL clusters.
 
 ### Config
 

docs/vendor/packaging-installer-storage.mdx

@@ -4,7 +4,7 @@ import KurlAvailability from "../partials/kurl/_kurl-availability.mdx"
 
 <KurlAvailability/>
 
-This topic provides guidance for selecting Replicated kURL add-ons to provide highly available data storage in embedded kURL clusters. For additional guidance, see [Choosing a PV Provisioner](https://kurl.sh/docs/create-installer/choosing-a-pv-provisioner) in the open source kURL documentation.
+This topic provides guidance for selecting Replicated kURL add-ons to provide highly available data storage in kURL clusters. For additional guidance, see [Choosing a PV Provisioner](https://kurl.sh/docs/create-installer/choosing-a-pv-provisioner) in the open source kURL documentation.
 
 ## Overview
 

docs/vendor/snapshots-overview.md

@@ -25,7 +25,7 @@ Full backups include the Admin Console and all application data, including KOTS-
 
 ### Other Object-Stored Data
 
-For embedded kURL clusters, you might be using object-stored data that is not specific to the kURL KOTS add-on. 
+For kURL clusters, you might be using object-stored data that is not specific to the kURL KOTS add-on. 
 
 For object-stored data that is not KOTS-specific and does not use persistentVolumeClaims (PVCs), you must write custom backup and restore hooks to enable back ups for that object-stored data. For example, Rook and Ceph do not use PVCs and so require custom backup and restore hooks. For more information about writing custom hooks, see [Configuring Backup and Restore Hooks](snapshots-hooks).
 

docs/vendor/telemetry-air-gap.mdx

@@ -48,7 +48,7 @@ When a limit is reached, the oldest events are purged until the payload is withi
 
 To collect telemetry from air gap instances:
 
-1. Ask your customer to collect a support bundle. See [Generating Support Bundles](/enterprise/support-bundle-generating).
+1. Ask your customer to collect a support bundle. See [Generating Support Bundles](/vendor/support-bundle-generating).
 
 1. After receiving the support bundle from your customer, go to the Vendor Portal **Customers**, **Customer Reporting**, or **Instance Details** page and upload the support bundle: