xrefs

Author: paigecalvert

docs/enterprise/updating-embedded.mdx

@@ -9,7 +9,7 @@ import Overview from "../partials/embedded-cluster/_update-overview.mdx"
 This topic describes how to perform updates for [Replicated Embedded Cluster](/vendor/embedded-overview) installations.
 
 :::note
-If you are instead looking for information about Replicated kURL, see [Performing Updates in kURL Clusters](updating-kurl).
+If you are instead looking for information about Replicated kURL, see [Perform Updates in kURL Clusters](updating-kurl).
 :::
 
 ## Overview

docs/enterprise/updating-kurl-about.mdx

@@ -4,7 +4,7 @@ import KurlAvailability from "../partials/kurl/_kurl-availability.mdx"
 
 <KurlAvailability/>
 
-This topic provides an overview of Replicated kURL cluster updates. For information about how to perform updates in kURL clusters, see [Performing Updates in kURL Clusters](updating-kurl).
+This topic provides an overview of Replicated kURL cluster updates. For information about how to perform updates in kURL clusters, see [Perform Updates in kURL Clusters](updating-kurl).
 
 ## Overview
 

docs/partials/getting-started/_test-your-changes.mdx

@@ -1 +1 @@
-Install the release to test your changes. For Embedded Cluster installations, see [Performing Udpates in Embedded Clusters](/enterprise/updating-embedded). For existing cluster installations with KOTS, see [Performing Updates in Existing Clusters](/enterprise/updating-app-manager).
+Install the release to test your changes. For Embedded Cluster installations, see [Performing Udpates in Embedded Clusters](/enterprise/updating-embedded). For existing cluster installations with KOTS, see [Perform Updates in Existing Clusters](/enterprise/updating-app-manager).

docs/reference/cron-expressions.md

@@ -2,7 +2,7 @@
 
 This topic describes the supported cron expressions that you can use to schedule automatic application update checks and automatic backups in the KOTS Admin Console.
 
-For more information, see [Configuring Automatic Updates](/enterprise/updating-apps) and [Schedule Automatic Backups](/enterprise/snapshots-creating#schedule-automatic-backups) in _Creating and Scheduling Backups_.
+For more information, see [Configure Automatic Updates](/enterprise/updating-apps) and [Schedule Automatic Backups](/enterprise/snapshots-creating#schedule-automatic-backups) in _Creating and Scheduling Backups_.
 
 ## Syntax
 

docs/vendor/embedded-overview.mdx

@@ -109,7 +109,7 @@ Embedded Cluster has the following limitations:
 
 * **Changing node hostnames is not supported**: After a host is added to a Kubernetes cluster, Kubernetes assumes that the hostname and IP address of the host will not change. If you need to change the hostname or IP address of a node, you must first remove the node from the cluster. For more information about the requirements for naming nodes, see [Node name uniqueness](https://kubernetes.io/docs/concepts/architecture/nodes/#node-name-uniqueness) in the Kubernetes documentation.
 
-* **Automatic updates not supported**: Configuring automatic updates from the Admin Console so that new versions are automatically deployed is not supported for Embedded Cluster installations. For more information, see [Configuring Automatic Updates](/enterprise/updating-apps).
+* **Automatic updates not supported**: Configuring automatic updates from the Admin Console so that new versions are automatically deployed is not supported for Embedded Cluster installations. For more information, see [Configure Automatic Updates](/enterprise/updating-apps).
 
 * **`minKotsVersion` and `targetKotsVersion` not supported**: The [`minKotsVersion`](/reference/custom-resource-application#minkotsversion-beta) and [`targetKotsVersion`](/reference/custom-resource-application#targetkotsversion) fields in the KOTS Application custom resource are not supported for Embedded Cluster installations. This is because each version of Embedded Cluster includes a particular version of KOTS. Setting `targetKotsVersion` or `minKotsVersion` to a version of KOTS that does not coincide with the version that is included in the specified version of Embedded Cluster will cause Embedded Cluster installations to fail with an error message like: `Error: This version of App Name requires a different version of KOTS from what you currently have installed`. To avoid installation failures, do not use targetKotsVersion or minKotsVersion in releases that support installation with Embedded Cluster.
 

docs/vendor/instance-insights-event-data.mdx

@@ -55,7 +55,7 @@ When installed alongisde the application in an online environment, KOTS automati
 * The instance checks for updates. By default, KOTS checks for updates every four hours. Additionally, an update check can occur when a user clicks the **Check for updates** button in the Replicated Admin Console. 
 
   :::note
-  KOTS users can modify or disable automatic update checks from the Admin Console. For more information, see [Configuring Automatic Updates](/enterprise/updating-apps).
+  KOTS users can modify or disable automatic update checks from the Admin Console. For more information, see [Configure Automatic Updates](/enterprise/updating-apps).
   :::
 
 * The status of an instance changes. For example, an instance can change from a Ready to Degraded status. For more information, see [Enabling and Understanding Application Status](insights-app-status).

docs/vendor/packaging-kots-versions.md

@@ -22,7 +22,7 @@ When you promote a new release specifying a minimum KOTS version that is later t
 
 The Admin Console temporarily displays an error message that informs the user that they must update KOTS before downloading the application version. This error also displays when the user checks for updates with the [`kots upstream upgrade`](/reference/kots-cli-upstream-upgrade) command.
 
-KOTS cannot update itself automatically, and users cannot update KOTS from the Admin Console. For more information on how to update KOTS in existing clusters or in kURL clusters, see [Performing Updates in Existing Clusters](/enterprise/updating-app-manager) and [Performing Updates in kURL Clusters](/enterprise/updating-kurl).
+KOTS cannot update itself automatically, and users cannot update KOTS from the Admin Console. For more information on how to update KOTS in existing clusters or in kURL clusters, see [Perform Updates in Existing Clusters](/enterprise/updating-app-manager) and [Performing Updates in kURL Clusters](/enterprise/updating-kurl).
 
 After updating KOTS to the minimum version or later, users can use the Admin Console or the [`kots upstream download`](/reference/kots-cli-upstream-download) command to download the release and subsequently deploy it.
 

docs/vendor/support-enabling-direct-bundle-uploads.md

@@ -12,7 +12,7 @@ When enabled, your customers can use the **Send bundle to vendor button** in the
 
 After clicking this button, the bundle will be immediately available under the Troubleshoot tab in the Vendor Portal team account associated with this customer.
 
-For more information on how your customer can use this feature, see [Generating Support Bundles from the Admin Console](/enterprise/troubleshooting-an-app).
+For more information on how your customer can use this feature, see [Generate Support Bundles from the Admin Console](/enterprise/troubleshooting-an-app).
 
 ### How to Enable Direct Bundle Uploads