diff --git a/content/docs/1.6.0/best-practices.md b/content/docs/1.6.0/best-practices.md
index 4a7a5c7d1..1077e12bf 100644
--- a/content/docs/1.6.0/best-practices.md
+++ b/content/docs/1.6.0/best-practices.md
@@ -95,7 +95,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li
 
 ## Volume Maintenance
 
-We highly recommend using the built-in backup feature of Longhorn.  A backup can be saved to an object store (S3, Azure, etc), to an NFS server, or to a SMB/CIFS server, although an object store is the preferred method.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store (such as S3 and Azure), an NFS server, or an SMB or CIFS server. Saving to an object store is preferable. 
 
 For each volume, schedule at least one recurring backup. If you must run Longhorn in production without a backupstore, then schedule at least one recurring snapshot for each volume.