diff --git a/kb/2023-12-27/best_practices_disk_performance.md b/kb/2023-12-27/best_practices_disk_performance.md
index cd8cbe31..306002a4 100644
--- a/kb/2023-12-27/best_practices_disk_performance.md
+++ b/kb/2023-12-27/best_practices_disk_performance.md
@@ -17,7 +17,7 @@ hide_table_of_contents: false
 
 # Best Practices for Optimizing Longhorn Disk Performance
 
-The Longhorn documentation provides [best practice recommendations](https://longhorn.io/docs/1.5.3/best-practices/) for deploying Longhorn in production environments. Before configuring workloads, ensure that you have set up the following basic requirements for optimal disk performance.
+The Longhorn documentation provides [best practice recommendations](https://longhorn.io/docs/1.6.0/best-practices/) for deploying Longhorn in production environments. Before configuring workloads, ensure that you have set up the following basic requirements for optimal disk performance.
 
 - SATA/NVMe SSDs or disk drives with similar performance
 - 10 Gbps network bandwidth between nodes
@@ -27,15 +27,15 @@ The following sections outline other recommendations for achieving optimal disk
 
 ## IO Performance
 
-- **Storage network**: Use a [dedicated storage network](https://docs.harvesterhci.io/v1.2/advanced/storagenetwork) to improve IO performance and stability.  
+- **Storage network**: Use a [dedicated storage network](https://docs.harvesterhci.io/v1.3/advanced/storagenetwork) to improve IO performance and stability.  
 
-- **Longhorn disk**: Use a [dedicated disk](https://docs.harvesterhci.io/v1.2/host/#multi-disk-management) for Longhorn storage instead of using the root disk.  
+- **Longhorn disk**: Use a [dedicated disk](https://docs.harvesterhci.io/v1.3/host/#multi-disk-management) for Longhorn storage instead of using the root disk.  
 
-- **Replica count**: Set the [default replica count](https://docs.harvesterhci.io/v1.2/advanced/storageclass#parameters-tab) to "2" to achieve data availability with better disk space usage or less impact to system performance. This practice is especially beneficial to data-intensive applications.  
+- **Replica count**: Set the [default replica count](https://docs.harvesterhci.io/v1.3/advanced/storageclass#parameters-tab) to "2" to achieve data availability with better disk space usage or less impact to system performance. This practice is especially beneficial to data-intensive applications.  
 
-- **Storage tag**: Use storage tags to define storage tiering for data-intensive applications. For example, only high-performance disks can be used for storing performance-sensitive data. You can either [add disks with tags](https://docs.harvesterhci.io/v1.2/host/#storage-tags) or [create StorageClasses with tags](https://docs.harvesterhci.io/v1.2/advanced/storageclass#disk-selector-optional).  
+- **Storage tag**: Use storage tags to define storage tiering for data-intensive applications. For example, only high-performance disks can be used for storing performance-sensitive data. You can either [add disks with tags](https://docs.harvesterhci.io/v1.3/host/#storage-tags) or [create StorageClasses with tags](https://docs.harvesterhci.io/v1.3/advanced/storageclass#disk-selector-optional).  
 
-- **Data locality**: Use `best-effort` as the default [data locality](https://longhorn.io/docs/1.5.3/high-availability/data-locality/) of Longhorn Storage Classes.  
+- **Data locality**: Use `best-effort` as the default [data locality](https://longhorn.io/docs/1.6.0/high-availability/data-locality/) of Longhorn Storage Classes.  
 
   For applications that support data replication (for example, a distributed database), you can use the `strict-local` option to ensure that only one replica is created for each volume. This practice prevents the extra disk space usage and IO performance overhead associated with volume replication.  
 
@@ -45,10 +45,10 @@ The following sections outline other recommendations for achieving optimal disk
 
 - **Recurring snapshots**: Periodically clean up system-generated snapshots and retain only the number of snapshots that makes sense for your implementation. 
 
-  For applications with replication capability, periodically [delete all types of snapshots](https://longhorn.io/docs/1.5.3/concepts/#243-deleting-snapshots).
+  For applications with replication capability, periodically [delete all types of snapshots](https://longhorn.io/docs/1.6.0/concepts/#243-deleting-snapshots).
 
 ## Disaster Recovery
 
-- **Recurring backups**: Create [recurring backup jobs](https://longhorn.io/docs/1.5.3/volumes-and-nodes/trim-filesystem/) for mission-critical application volumes.
+- **Recurring backups**: Create [recurring backup jobs](https://longhorn.io/docs/1.6.0/snapshots-and-backups/scheduling-backups-and-snapshots/) for mission-critical application volumes.
 
 - **System backup**: Run periodic system backups.
\ No newline at end of file