Edit xrefs in vendor

paigecalvert · paigecalvert · commit c37bbaa77c21 · 2025-04-08T21:52:41.000-06:00
diff --git a/docs/vendor/admin-console-customize-config-screen.md b/docs/vendor/admin-console-customize-config-screen.md
@@ -132,4 +132,4 @@ To add fields to the Admin Console configuration screen:
 
 After you add user input fields to the configuration screen, you use template functions to map the user-supplied values to manifest files in your release. If you use a Helm chart for your application, you map the values to the Helm chart `values.yaml` file using the HelmChart custom resource.
 
-For more information, see [Mapping User-Supplied Values](config-screen-map-inputs).
+For more information, see [Map User-Supplied Values](config-screen-map-inputs).
diff --git a/docs/vendor/helm-image-registry.mdx b/docs/vendor/helm-image-registry.mdx
@@ -124,10 +124,10 @@ To enable the proxy registry:
       ```
 
       :::note
-      If you configured a custom domain for the proxy registry, use the custom domain instead of `proxy.replicated.com`. For more information, see [Using Custom Domains](custom-domains-using).
+      If you configured a custom domain for the proxy registry, use the custom domain instead of `proxy.replicated.com`. For more information, see [Use Custom Domains](custom-domains-using).
       :::
    
-   1. Log in to the Replicated registry and install the chart, passing the local `values.yaml` file you created with the `--values` flag. See [Installing with Helm](install-with-helm).
+   1. Log in to the Replicated registry and install the chart, passing the local `values.yaml` file you created with the `--values` flag. See [Install with Helm](install-with-helm).
 
 
     
diff --git a/docs/vendor/helm-native-about.mdx b/docs/vendor/helm-native-about.mdx
@@ -72,7 +72,7 @@ The following limitations apply when deploying Helm charts with the `kots.io/v1b
 
 * When updating the HelmChart custom resource in a release from `kots.io/v1beta1` to `kots.io/v1beta2`, the diff viewer shows a large diff because the underlying file structure of the rendered manifests is different.
 
-* Editing downstream Kustomization files to make changes to the application before deploying is not supported. This is because KOTS does not use Kustomize when installing Helm charts with the `kots.io/v1beta2` HelmChart custom resource. For more information about patching applications with Kustomize, see [Patching with Kustomize](/enterprise/updating-patching-with-kustomize).
+* Editing downstream Kustomization files to make changes to the application before deploying is not supported. This is because KOTS does not use Kustomize when installing Helm charts with the `kots.io/v1beta2` HelmChart custom resource. For more information about patching applications with Kustomize, see [Patch with Kustomize](/enterprise/updating-patching-with-kustomize).
 
 * <GitOpsLimitation/>
 
@@ -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).
+   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 [Patch 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.
 
diff --git a/docs/vendor/instance-insights-details.md b/docs/vendor/instance-insights-details.md
@@ -31,7 +31,7 @@ As shown in the image above, the **Instance details** page includes the followin
 * **Current State**: Information about the state of the instance, such as the current application version. See [Current State](#current-state) below.
 * **Instance Insights**: Key performance indicators (KPIs) related to health, performance, and adoption. See [Insights](#insights) below. 
 * **Instance Information**: Information about the cluster where the instance is installed, such as the version of Kubernetes running on the cluster. See [Instance Information](#instance-information) below.
-* **Custom Metrics**: The values for any custom metrics that are configured for the application, from the most recent check-in. For more information about configuring custom metrics, see [Configuring Custom Metrics](/vendor/custom-metrics).
+* **Custom Metrics**: The values for any custom metrics that are configured for the application, from the most recent check-in. For more information about configuring custom metrics, see [Configure Custom Metrics](/vendor/custom-metrics).
 * **Instance Uptime**: Details about instance uptime over time. See [Instance Uptime](#instance-uptime) below.
 * **Instance Activity**: Event data stream. See [Instance Activity](#instance-activity) below.
 
@@ -302,7 +302,7 @@ The following tables describe the events that can be displayed in the **Instance
 
 You can filter the activity feed by any custom metrics that are configured for the application. The labels for the custom metrics vary depending on the custom key value pairs included in the data set that is sent to the Vendor Portal. For example, the key value pair `"num_projects": 5` is displayed as **Num Projects: 5** in the activity feed.
 
-For more information about configuring custom metrics, see [Configuring Custom Metrics](/vendor/custom-metrics).
+For more information about configuring custom metrics, see [Configure Custom Metrics](/vendor/custom-metrics).
 #### Infrastructure status {#infrastructure}
 
 <table>
diff --git a/docs/vendor/kots-faq.mdx b/docs/vendor/kots-faq.mdx
@@ -154,6 +154,8 @@ The KOTS Admin Console and the Replicated Download Portal support the use of a c
 
 For more information, see [Customizing the Admin Console and Download Portal](/vendor/admin-console-customize-app-icon) and [About Custom Domains](custom-domains).
 
+For more information, see [Use Custom Domains](/vendor/custom-domains-using).
+
 ## Replicated SDK FAQs
 
 ### What is the SDK?
@@ -200,7 +202,7 @@ Yes. Replicated supports the use of custom domains to alias the endpoints for Re
 
 Replicated domains are external to your domain and can require additional security reviews by your customer. Using custom domains as aliases can bring the domains inside an existing security review and reduce your exposure.
 
-For more information, see [Using Custom Domains](/vendor/custom-domains-using).
+For more information, see [Use Custom Domains](/vendor/custom-domains-using).
 
 ### How does Replicated collect telemetry from instances of my application?
 
diff --git a/docs/vendor/packaging-public-images.mdx b/docs/vendor/packaging-public-images.mdx
@@ -17,7 +17,7 @@ docker pull REPLICATED_PROXY_DOMAIN/proxy/APPSLUG/UPSTREAM_REGISTRY_HOSTNAME/IMA
 ```
 Where:
 * `APPSLUG` is your Replicated app slug found on the [app settings page](https://vendor.replicated.com/settings).
-* `REPLICATED_PROXY_DOMAIN` is `proxy.replicated.com` or your custom domain. For information about how to set a custom domain for the proxy registry, see [Using Custom Domains](/vendor/custom-domains-using). 
+* `REPLICATED_PROXY_DOMAIN` is `proxy.replicated.com` or your custom domain. For information about how to set a custom domain for the proxy registry, see [Use Custom Domains](/vendor/custom-domains-using). 
 * `UPSTREAM_REGISTRY_HOSTNAME` is the hostname for the public registry where the image is located. If the image is located in a namespace within the registry, include the namespace after the hostname. For example, `quay.io/namespace`.
 * `IMAGE` is the image name.
 * `TAG` is the image tag.
@@ -55,7 +55,7 @@ The following example shows how to pull a public image when a custom domain is c
 ```bash
 docker pull my.customdomain.io/proxy/APPSLUG/public.ecr.aws/nginx/nginx:latest
 ```
-For information about how to set a custom domain for the proxy registry, see [Using Custom Domains](/vendor/custom-domains-using). 
+For information about how to set a custom domain for the proxy registry, see [Use Custom Domains](/vendor/custom-domains-using). 
 
 ## Related Topic
 
diff --git a/docs/vendor/private-images-kots.mdx b/docs/vendor/private-images-kots.mdx
@@ -70,4 +70,6 @@ To enable the proxy registry:
 
     * **Kubernetes Operators**: For applications packaged with Kubernetes Operators, KOTS cannot modify pods that are created at runtime by the Operator. To support the use of private images in all environments, the Operator code should use KOTS functionality to determine the image name and image pull secrets for all pods when they are created. For instructions, see [Referencing Images](/vendor/operator-referencing-images) in the _Packaging Kubernetes Operators_ section.
 
-1. If you are deploying Pods to namespaces other than the application namespace, add the namespace to the `additionalNamespaces` attribute of the KOTS Application custom resource. This ensures that KOTS can provision the `imagePullSecret` in the namespace to allow the Pod to pull the image. For instructions, see [Defining Additional Namespaces](operator-defining-additional-namespaces).
+1. If you are deploying Pods to namespaces other than the application namespace, add the namespace to the `additionalNamespaces` attribute of the KOTS Application custom resource. This ensures that KOTS can provision the `imagePullSecret` in the namespace to allow the Pod to pull the image. For instructions, see [Defining Additional Namespaces](operator-defining-additional-namespaces).
+
+1. (Optional) Add a custom domain for the proxy registry instead of `proxy.replicated.com`. See [Use Custom Domains](custom-domains-using).
diff --git a/docs/vendor/releases-about.mdx b/docs/vendor/releases-about.mdx
@@ -48,11 +48,11 @@ The following describes each of the channel settings:
 * **Set this channel to default**: When enabled, sets the channel as the default channel. The default channel cannot be archived.
 * **Custom domains**: Select the customer-facing domains that releases promoted to this channel use for the Replicated registry, Replicated proxy registry, Replicated app service, or Replicated Download Portal endpoints. If a default custom domain exists for any of these endpoints, choosing a different domain in the channel settings overrides the default. If no custom domains are configured for an endpoint, the drop-down for the endpoint is disabled.
 
-  For more information about configuring custom domains and assigning default domains, see [Using Custom Domains](custom-domains-using).
+  For more information about configuring custom domains and assigning default domains, see [Use Custom Domains](custom-domains-using).
 * The following channel settings apply only to applications that support KOTS:
     * **Automatically create airgap builds for newly promoted releases in this channel**: When enabled, the Vendor Portal automatically builds an air gap bundle when a new release is promoted to the channel. When disabled, you can generate an air gap bundle manually for a release on the **Release History** page for the channel.
     * **Enable semantic versioning**: When enabled, the Vendor Portal verifies that the version label for any releases promoted to the channel uses a valid semantic version. For more information, see [Semantic Versioning](releases-about#semantic-versioning) in _About Releases_.
-    * **Enable new airgap bundle format**: When enabled, air gap bundles built for releases promoted to the channel use a format that supports image digests. This air gap bundle format also ensures that identical image layers are not duplicated, resulting in a smaller air gap bundle size. For more information, see [Using Image Digests in Air Gap Installations](private-images-tags-digests#digests-air-gap) in _Using Image Tags and Digests_.
+    * **Enable new airgap bundle format**: When enabled, air gap bundles built for releases promoted to the channel use a format that supports image digests. This air gap bundle format also ensures that identical image layers are not duplicated, resulting in a smaller air gap bundle size. For more information, see [Use Image Digests in Air Gap Installations](private-images-tags-digests#digests-air-gap) in _Use Image Tags and Digests_.
 
       :::note
       The new air gap bundle format is supported for applications installed with KOTS v1.82.0 or later. 
diff --git a/docs/vendor/releases-creating-channels.md b/docs/vendor/releases-creating-channels.md
@@ -20,7 +20,7 @@ To create a channel:
 1. Enter a name and description for the channel.
 1. (Recommended) Enable semantic versioning on the channel if it is not enabled by default by turning on **Enable semantic versioning**. For more information about semantic versioning and defaults, see [Semantic Versioning](releases-about#semantic-versioning).
 
-1. (Recommended) Enable an air gap bundle format that supports image digests and deduplication of image layers, by turning on **Enable new air gap bundle format**. For more information, see [Using Image Tags and Digests](private-images-tags-digests).
+1. (Recommended) Enable an air gap bundle format that supports image digests and deduplication of image layers, by turning on **Enable new air gap bundle format**. For more information, see [Use Image Tags and Digests](private-images-tags-digests).
 
 1. Click **Create Channel**.
 
diff --git a/docs/vendor/replicated-sdk-installing.mdx b/docs/vendor/replicated-sdk-installing.mdx
@@ -9,7 +9,7 @@ This topic describes the methods for distributing and installing the Replicated
 
 It includes information about how to install the SDK alongside Helm charts or Kubernetes manifest-based applications using the Helm CLI or a Replicated installer (Replicated KOTS, kURL, Embedded Cluster). It also includes information about installing the SDK as a standalone component in integration mode.
 
-For information about installing the SDK in air gap mode, see [Installing the SDK in Air Gap Environments](replicated-sdk-airgap).
+For information about installing the SDK in air gap mode, see [Install the SDK in Air Gap Environments](replicated-sdk-airgap).
 
 ## Requirement
 
diff --git a/docs/vendor/snapshots-overview.mdx b/docs/vendor/snapshots-overview.mdx
@@ -22,13 +22,13 @@ When snapshots is enabled for your application, your customers can manage and pe
 
 Snapshots uses the Velero open source project as the backend to back up Kubernetes manifests and persistent volumes. Velero is a mature, fully-featured application. For more information, see the [Velero documentation](https://velero.io/docs/).
 
-In addition to the default functionality that Velero provides, KOTS exposes hooks that let you inject scripts that can execute both before and after a backup, and before and after a restore. For more information, see [Configuring Backup and Restore Hooks for Snapshots](/vendor/snapshots-hooks).
+In addition to the default functionality that Velero provides, KOTS exposes hooks that let you inject scripts that can execute both before and after a backup, and before and after a restore. For more information, see [Configure Backup and Restore Hooks for Snapshots](/vendor/snapshots-hooks).
 
 ### Limitations and Considerations
 
 * <NoEcSupport/>
 
-- The snapshots feature is available only for licenses with the **Allow Snapshots** option enabled. For more information, see [Creating and Managing Customers](/vendor/releases-creating-customer).
+- The snapshots feature is available only for licenses with the **Allow Snapshots** option enabled. For more information, see [Create and Manage Customers](/vendor/releases-creating-customer).
 
 - Snapshots are useful for rollback and disaster recovery scenarios. They are not intended to be used for application migration.
 
@@ -101,13 +101,13 @@ Full backups include the Admin Console and all application data, including KOTS-
 
 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 for Snapshots](snapshots-hooks).
+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 [Configure Backup and Restore Hooks for Snapshots](snapshots-hooks).
 
 #### Pod Volume Data
 
 Replicated supports only the restic backup program for pod volume data.
 
-By default, Velero requires that you opt-in to have pod volumes backed up. In the Backup resource that you configure to enable snapshots, you must annotate each specific volume that you want to back up. For more information about including and excluding pod volumes, see [Configuring Snapshots](/vendor/snapshots-configuring-backups).
+By default, Velero requires that you opt-in to have pod volumes backed up. In the Backup resource that you configure to enable snapshots, you must annotate each specific volume that you want to back up. For more information about including and excluding pod volumes, see [Configure Snapshots](/vendor/snapshots-configuring-backups).
 
 ## About Restores {#restores}
 
@@ -119,7 +119,7 @@ Then, the restore process redeploys all of the application manifests. All Pods a
 
 When you restore the Admin Console only, no changes are made to the application.
 
-For information about how to restore using the Admin Console or the KOTS CLI, see [Restoring from Backups](/enterprise/snapshots-restoring-full).
+For information about how to restore using the Admin Console or the KOTS CLI, see [Restore from Backups](/enterprise/snapshots-restoring-full).
 
 ## Using Snapshots
 
@@ -130,9 +130,9 @@ This section provides an overview of how vendors and enterprise users can config
 To enable the snapshots backup and restore feature for your users, you must:
 
 - Have the snapshots entitlement enabled in your Replicated vendor account. For account entitlements, contact the Replicated TAM team.
-- Define a manifest for creating backups. See [Configuring Snapshots](snapshots-configuring-backups).
-- When needed, configure backup and restore hooks. See [Configuring Backup and Restore Hooks for Snapshots](snapshots-hooks).
-- Enable the **Allow Snapshot** option in customer licenses. See [Creating and Managing Customers](releases-creating-customer).
+- Define a manifest for creating backups. See [Configure Snapshots](snapshots-configuring-backups).
+- When needed, configure backup and restore hooks. See [Configure Backup and Restore Hooks for Snapshots](snapshots-hooks).
+- Enable the **Allow Snapshot** option in customer licenses. See [Create and Manage Customers](releases-creating-customer).
 
 ### Understanding Backup and Restore for Users {#how-users}
 
diff --git a/docs/vendor/support-inspecting-support-bundles.md b/docs/vendor/support-inspecting-support-bundles.md
@@ -26,7 +26,7 @@ To inspect a support bundle:
 
 1. (Optional) Click **Download bundle** to download the bundle. This can be helpful if you want to access the bundle from another system or if other team members want to access the bundle and use other tools to examine the files.
 
-1. (Optional) Navigate back to the [**Troubleshoot**](https://vendor.replicated.com/troubleshoot) page and click **Create cluster** to provision a cluster with Replicated Compatibility Matrix. This can be helpful for creating customer-representative environments for troubleshooting. For more information about creating clusters with Compatibility Matrix, see [Using Compatibility Matrix](testing-how-to).
+1. (Optional) Navigate back to the [**Troubleshoot**](https://vendor.replicated.com/troubleshoot) page and click **Create cluster** to provision a cluster with Replicated Compatibility Matrix. This can be helpful for creating customer-representative environments for troubleshooting. For more information about creating clusters with Compatibility Matrix, see [Use Compatibility Matrix](testing-how-to).
 
     <img alt="Cluster configuration dialog" src="/images/cmx-cluster-configuration.png" width="400px"/>
 
diff --git a/docs/vendor/team-management.md b/docs/vendor/team-management.md
diff --git a/docs/vendor/telemetry-air-gap.mdx b/docs/vendor/telemetry-air-gap.mdx

Original file line number	Diff line number	Diff line change
`@@ -132,4 +132,4 @@ To add fields to the Admin Console configuration screen:`
`132`	`132`
`133`	`133`	After you add user input fields to the configuration screen, you use template functions to map the user-supplied values to manifest files in your release. If you use a Helm chart for your application, you map the values to the Helm chart `values.yaml` file using the HelmChart custom resource.
`134`	`134`
`135`		`-For more information, see [Mapping User-Supplied Values](config-screen-map-inputs).`
	`135`	`+For more information, see [Map User-Supplied Values](config-screen-map-inputs).`