update xrefs in reference dir

paigecalvert · paigecalvert · commit 1c04ddea5307 · 2025-04-09T10:17:56.000-06:00
diff --git a/docs/reference/custom-resource-application.mdx b/docs/reference/custom-resource-application.mdx
@@ -333,7 +333,7 @@ spec:
 ## proxyRegistryDomain
 
 :::important
-`proxyRegistryDomain` is deprecated. For information about how to use a custom domain for the Replicated proxy registry, see [Using Custom Domains](/vendor/custom-domains-using).
+`proxyRegistryDomain` is deprecated. For information about how to use a custom domain for the Replicated proxy registry, see [Use Custom Domains](/vendor/custom-domains-using).
 :::
 
 <table>	
@@ -354,7 +354,7 @@ spec:
 ## replicatedRegistryDomain
 
 :::important
-`replicatedRegistryDomain` is deprecated. For information about how to use a custom domain for the Replicated registry, see [Using Custom Domains](/vendor/custom-domains-using).
+`replicatedRegistryDomain` is deprecated. For information about how to use a custom domain for the Replicated registry, see [Use Custom Domains](/vendor/custom-domains-using).
 :::
 
 <table>	
diff --git a/docs/reference/custom-resource-backup.md b/docs/reference/custom-resource-backup.md
@@ -157,5 +157,5 @@ However, not all fields are supported for full backups. The table below lists th
   Some of these fields are supported for hook arrays, as described in the previous field definition table. See [Supported Fields for Full Backups with Snapshots](#fields) above.
   :::
 
-- All resources are included in the backup by default. However, resources can be excluded by adding `velero.io/exclude-from-backup=true` to the manifest files that you want to exclude. For more information, see [Configuring Snapshots](/vendor/snapshots-configuring-backups).
+- All resources are included in the backup by default. However, resources can be excluded by adding `velero.io/exclude-from-backup=true` to the manifest files that you want to exclude. For more information, see [Configure Snapshots](/vendor/snapshots-configuring-backups).
 
diff --git a/docs/reference/custom-resource-helmchart-v2.mdx b/docs/reference/custom-resource-helmchart-v2.mdx
@@ -97,7 +97,7 @@ The `builder` key is required for the following use cases:
 
   <BuilderAirgapIntro/>
 
-  For more information, see [Packaging Air Gap Bundles for Helm Charts](/vendor/helm-packaging-airgap-bundles).
+  For more information, see [Package Air Gap Bundles for Helm Charts](/vendor/helm-packaging-airgap-bundles).
 
 * To support online installations that use a local private registry, the `builder` field renders the Helm chart with all of the necessary images so that KOTS knows where to pull the images.
 
diff --git a/docs/reference/embedded-config.mdx b/docs/reference/embedded-config.mdx
@@ -1,6 +1,6 @@
 # Embedded Cluster Config
 
-This topic is a reference for the Replicated Embedded Cluster Config custom resource. For more information about Embedded Cluster, see [Using Embedded Cluster](/vendor/embedded-overview).
+This topic is a reference for the Replicated Embedded Cluster Config custom resource. For more information about Embedded Cluster, see [Use Embedded Cluster](/vendor/embedded-overview).
 
 ## Overview
 
diff --git a/docs/reference/replicated-cli-installing.mdx b/docs/reference/replicated-cli-installing.mdx
@@ -14,7 +14,7 @@ You can use the Replicated CLI to manage your applications with Replicated progr
 
 Complete the following prerequisites before installing the Replicated CLI:
 
-- Create a vendor account. See [Creating a Vendor Account](/vendor/vendor-portal-creating-account).
+- Create a vendor account. See [Create a Vendor Account](/vendor/vendor-portal-creating-account).
 - To run on Linux or Mac, install [curl](https://curl.haxx.se/).
 - To run through a Docker container, install [docker](https://www.docker.com).
 
diff --git a/docs/reference/replicated-sdk-apis.md b/docs/reference/replicated-sdk-apis.md
@@ -122,7 +122,7 @@ Response:
 
 ### POST /app/custom-metrics
 
-Send custom application metrics. For more information and examples see [Configuring Custom Metrics](/vendor/custom-metrics).
+Send custom application metrics. For more information and examples see [Configure Custom Metrics](/vendor/custom-metrics).
 
 ### PATCH /app/custom-metrics
 
@@ -490,7 +490,7 @@ To revoke access to your application when a license expires:
 
   [View a larger version of this image](/images/customer-expiration-policy.png)
 
-1. Install the Replicated SDK as a standalone component in your cluster. This is called _integration mode_. Installing in integration mode allows you to develop locally against the SDK API without needing to create releases for your application in the vendor portal. See [Developing Against the SDK API](/vendor/replicated-sdk-development).
+1. Install the Replicated SDK as a standalone component in your cluster. This is called _integration mode_. Installing in integration mode allows you to develop locally against the SDK API without needing to create releases for your application in the vendor portal. See [Develop Against the SDK API](/vendor/replicated-sdk-development).
 
 1. In your application, use the `/api/v1/license/fields/expires_at` endpoint to get the `expires_at` field that you defined in the previous step.
 
@@ -515,4 +515,4 @@ To revoke access to your application when a license expires:
 
 1. Add logic to your application to revoke access if the current date and time is more recent than the expiration date of the license.
 
-1. (Recommended) Use signature verification in your application to ensure the integrity of the license field. See [Verifying License Field Signatures with the Replicated SDK API](/vendor/licenses-verify-fields-sdk-api).
+1. (Recommended) Use signature verification in your application to ensure the integrity of the license field. See [Verify License Field Signatures with the Replicated SDK API](/vendor/licenses-verify-fields-sdk-api).
diff --git a/docs/reference/template-functions-config-context.md b/docs/reference/template-functions-config-context.md
@@ -42,7 +42,7 @@ spec:
         nodePort: repl{{ ConfigOption "myapp_load_balancer_node_port"}}
         annotations: repl{{ ConfigOption `myapp_load_balancer_annotations` | nindent 14 }}
 ```
-For more information, see [Setting Helm Values with KOTS](/vendor/helm-optional-value-keys).
+For more information, see [Set Helm Values with KOTS](/vendor/helm-optional-value-keys).
 
 ## ConfigOptionData
 
@@ -78,7 +78,7 @@ spec:
         cert: repl{{ print `|`}}repl{{ ConfigOptionData `tls_certificate_file` | nindent 12 }}
         key: repl{{ print `|`}}repl{{ ConfigOptionData `tls_private_key_file` | nindent 12 }}
 ```
-For more information, see [Setting Helm Values with KOTS](/vendor/helm-optional-value-keys).
+For more information, see [Set Helm Values with KOTS](/vendor/helm-optional-value-keys).
 
 ## ConfigOptionFilename
 
@@ -178,7 +178,7 @@ spec:
     postgresql:
       enabled: repl{{ ConfigOptionEquals `postgres_type` `embedded_postgres`}}
 ```
-For more information, see [Setting Helm Values with KOTS](/vendor/helm-optional-value-keys).
+For more information, see [Set Helm Values with KOTS](/vendor/helm-optional-value-keys).
 
 ## ConfigOptionNotEquals
 
@@ -232,7 +232,7 @@ spec:
         repository: '{{repl HasLocalRegistry | ternary LocalRegistryNamespace "proxy/myapp/quay.io/my-org" }}/nginx'
         tag: v1.0.1
 ```
-For more information, see [Setting Helm Values with KOTS](/vendor/helm-optional-value-keys).
+For more information, see [Set Helm Values with KOTS](/vendor/helm-optional-value-keys).
 
 ## LocalRegistryNamespace
 
@@ -263,7 +263,7 @@ spec:
         repository: '{{repl HasLocalRegistry | ternary LocalRegistryNamespace "proxy/myapp/quay.io/my-org" }}/nginx'
         tag: v1.0.1
 ```
-For more information, see [Setting Helm Values with KOTS](/vendor/helm-optional-value-keys).
+For more information, see [Set Helm Values with KOTS](/vendor/helm-optional-value-keys).
 
 ## LocalImageName
 
@@ -273,7 +273,7 @@ func LocalImageName(remoteImageName string) string
 
 Given a `remoteImageName`, rewrite the `remoteImageName` so that it can be pulled to local hosts.
 
-A common use case for the `LocalImageName` function is to ensure that a Kubernetes Operator can determine the names of container images on Pods created at runtime. For more information, see [Referencing Images](/vendor/operator-referencing-images) in the _Packaging a Kubernetes Operator Application_ section.
+A common use case for the `LocalImageName` function is to ensure that a Kubernetes Operator can determine the names of container images on Pods created at runtime. For more information, see [Reference Images](/vendor/operator-referencing-images) in the _Packaging a Kubernetes Operator Application_ section.
 
 `LocalImageName` rewrites the `remoteImageName` in one of the following ways, depending on if a private registry is configured and if the image must be proxied:
 
@@ -374,4 +374,4 @@ spec:
         repository: '{{repl HasLocalRegistry | ternary LocalRegistryNamespace "proxy/myapp/quay.io/my-org" }}/nginx'
         tag: v1.0.1
 ```
-For more information, see [Setting Helm Values with KOTS](/vendor/helm-optional-value-keys).
+For more information, see [Set Helm Values with KOTS](/vendor/helm-optional-value-keys).
