edits and xref fixes

Author: paigecalvert

docs/enterprise/snapshots-troubleshooting-backup-restore.md

@@ -160,7 +160,7 @@ There are file changes between Restic's initial scan of the volume and during th
 
 To resolve this issue, do one of the following:
 
-* Use [Snapshot Hooks](https://docs.replicated.com/vendor/snapshots-hooks) to export data to an [EmptyDir](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) volume and include that in the backup instead of the primary PVC volume.
+* Use [hooks](/vendor/snapshots-hooks) to export data to an [EmptyDir](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) volume and include that in the backup instead of the primary PVC volume. See [Configuring Backup and Restore Hooks for Snapshots](/vendor/snapshots-hooks).
 * Freeze the file system to ensure all pending disk I/O operations have completed prior to taking a snapshot. For more information, see [Hook Example with fsfreeze](https://velero.io/docs/main/backup-hooks/#hook-example-with-fsfreeze) in the Velero documentation.
 
 

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 Backups](/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 [Configuring Snapshots](/vendor/snapshots-configuring-backups).
 

docs/vendor/replicated-onboarding.mdx

@@ -545,7 +545,7 @@ Enable backup and restore with Velero for your application so that users can bac
 
 There are different steps to configure backup and restore for Embedded Cluster and for existing cluster installations with KOTS:
 * To configure the disaster recovery feature for Embedded Cluster, see [Disaster Recovery for Embedded Cluster](/vendor/embedded-disaster-recovery)
-* To configure the snapshots feature for existing cluster KOTS installations, see [Configuring Backup and Restore](snapshots-configuring-backups).
+* To configure the snapshots feature for existing cluster KOTS installations, see [Configuring Snapshots](snapshots-configuring-backups).
 
 ### Add Custom Metrics
 

docs/vendor/snapshots-configuring-backups.md

@@ -1,14 +1,14 @@
-# Enabling and Configuring Snapshots
+# Configuring Snapshots
 
 This topic provides information about how to configure the Velero Backup resource to enable Replicated KOTS snapshots for an application.
 
 For more information about snapshots, see [About Backup and Restore with snapshots](/vendor/snapshots-overview).
 
-## Configure the Velero Backup Resource
+## Configure Snapshots
 
 Add a Velero Backup custom resource (`kind: Backup`, `apiVersion: velero.io/v1`) to your release and configure it as needed. After configuring the Backup resource, add annotations for each volume that you want to be included in backups.
 
-To configure the Velero Backup Resource for snapshots:
+To configure snapshots for your application:
 
 1. Log in to the[ Vendor Portal](https://vendor.replicated.com) and create a new release containing your application files.
 
@@ -26,7 +26,7 @@ To configure the Velero Backup Resource for snapshots:
 
     For more information about the Velero Backup resource, including limitations, the list of supported fields for snapshots, and an example, see [Velero Backup Resource for Snapshots](/reference/custom-resource-backup).
 
-1. (Optional) Configure backup and restore hooks in the Backup resource. For more information, see [Configuring Velero Backup and Restore Hooks for Snapshots](snapshots-hooks).
+1. (Optional) Configure backup and restore hooks in the Backup resource. For more information, see [Configuring Backup and Restore Hooks for Snapshots](snapshots-hooks).
 
 1. For each volume that requires a backup, add the `backup.velero.io/backup-volumes` annotation. The annotation name is `backup.velero.io/backup-volumes` and the value is a comma separated list of volumes to include in the backup.
 

docs/vendor/snapshots-overview.mdx

@@ -22,7 +22,7 @@ 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](/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 [Configuring Backup and Restore Hooks for Snapshots](/vendor/snapshots-hooks).
 
 ### Limitations and Considerations
 
@@ -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](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 [Configuring 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 Backups](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 [Configuring Snapshots](/vendor/snapshots-configuring-backups).
 
 ## About Restores {#restores}
 
@@ -123,13 +123,15 @@ For information about how to restore using the Admin Console or the KOTS CLI, se
 
 ## Using Snapshots
 
+This section provides an overview of how vendors and enterprise users can configure and use the snapshots feature.
+
 ### How to Enable Snapshots for Your Application
 
 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 Backups](snapshots-configuring-backups).
-- When needed, configure backup and restore hooks. See [Configuring Backup and Restore Hooks](snapshots-hooks).
+- 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).
 
 ### Understanding Backup and Restore for Users {#how-users}