diff --git a/bvm-configure.md b/bvm-configure.md
index 37431372..55a55439 100644
--- a/bvm-configure.md
+++ b/bvm-configure.md
@@ -38,7 +38,7 @@ You need to create the Service2Service authorization policy between source bucke
 
 Buckets require permission to perform the `cloud-object-storage.backup-vault.sync` operation to a `BackupVault`. It is granted by using service-to-service policy, and must be configured even if the bucket and backup vault are in the same account or serviceInstance.
 
-See [Getting Started with IAM](https://test.cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam) and [Identity and Access Management actions](https://test.cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam#iam-actions) on more details for configuring service-to-service permissions.
+See [Getting Started with IAM](docs/cloud-object-storage?topic=cloud-object-storage-getting-started-with-iam) and [Identity and Access Management actions](docs/cloud-object-storage?topic=cloud-object-storage-getting-started-with-iam#iam-actions) on more details for configuring service-to-service permissions.
 
 ## Adding a backup policy to a bucket
 
diff --git a/bvm-faq.md b/bvm-faq.md
index 6ce27968..2d636e1a 100644
--- a/bvm-faq.md
+++ b/bvm-faq.md
@@ -70,6 +70,6 @@ It is the user's responsibility to monitor for and remediate `BackupPolicy` sync
 {: #faq-backup-vault-mgmt-identical-source}
 {: faq}
 
-Not all actions performed on the source-bucket are synced to the `BackupVault`. If Restore operations need to result in an identical copy of the source bucket, then it is the user's responsibility to not perform actions that are not synced. For more information on what is synced, go to [Configure backups](/docs/cloud-object-storage?topic=cloud-object-storage-bvm-configure).
+Not all actions performed on the source-bucket are synced to the `BackupVault`. If Restore operations need to result in an identical copy of the source bucket, then it is the user's responsibility to not perform actions that are not synced. For more information on what is synced, go to [Configure backups](/docs/cloud-object-storage?topic=cloud-object-storage-configuring-backups).
 
 It is our recommendation that the Restore target bucket be empty in order to avoid conflicts with restored objects. The Restore target bucket should also not have a `BackupPolicy` enabled on it. Restore to the source bucket is possible, but it is recommended that the `BackupPolicy` be deleted before beginning a Restore and then reenabled once Restore is complete.
diff --git a/bvm-overview.md b/bvm-overview.md
index 7ecb5d0f..b4a64da8 100644
--- a/bvm-overview.md
+++ b/bvm-overview.md
@@ -49,7 +49,7 @@ Target bucket              | A {{site.data.keyword.cos_full_notm}} bucket that r
 
 Whereas periodic backup solutions take individual "snapshots" of data for a given point-in-time, {{site.data.keyword.cos_full_notm}} produces backup coverage of a bucket over a range of time, providing users the ability to restore to any specific point in time contained within a `RecoveryRange`. This more granular approach provides more flexibility for users, and the ability to achieve lower Recovery Point Objectives that are not limited by the amount of time it takes to scan a bucket for changes since the last backup.
 
-`RecoveryRanges` are created within a `BackupVault` whenever a new `BackupPolicy` targeting the `BackupVault` is set on a {{site.data.keyword.cos_full_notm}} bucket. `RecoveryRanges` receives new data as long as the associated `BackupPolicy` is enabled and active. For details on creating and monitoring a `BackupPolicy`, see [Configuring backups](/docs/cloud-object-storage?topic=cloud-object-storage-bvm-configure).
+`RecoveryRanges` are created within a `BackupVault` whenever a new `BackupPolicy` targeting the `BackupVault` is set on a {{site.data.keyword.cos_full_notm}} bucket. `RecoveryRanges` receives new data as long as the associated `BackupPolicy` is enabled and active. For details on creating and monitoring a `BackupPolicy`, see [Configuring backups](/docs/cloud-object-storage?topic=cloud-object-storage-configuring-backups).
 
 Users can list the RecoveryRanges present within a BackupVault using the following commands:
 
diff --git a/bvm-restore.md b/bvm-restore.md
index 266fb25c..6e0dc88a 100644
--- a/bvm-restore.md
+++ b/bvm-restore.md
@@ -36,7 +36,7 @@ Backup data is stored in a Backup Vault in the form of Recovery Ranges. Each Rec
 
 Backup vaults require permission to perform the "cloud-object-storage.bucket.restore_sync" operation to a target bucket. It is granted by using service-to-service policy, and must be configured even if the backup vault and bucket are in the same account or service instance.
 
-See [Getting Started with IAM](https://test.cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam) and [Identity and Access Management actions](https://test.cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam#iam-actions) on more details for configuring service-to-service permissions.
+See [Getting Started with IAM](docs/cloud-object-storage?topic=cloud-object-storage-getting-started-with-iam) and [Identity and Access Management actions](docs/cloud-object-storage?topic=cloud-object-storage-getting-started-with-iam#iam-actions) on more details for configuring service-to-service permissions.
 
 
 ### Concurrent restore limit