Make modifications requested in PR review.

Signed-off-by: James Munson <[email protected]>

content/docs/1.4.0/best-practices.md

@@ -94,7 +94,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li
 
 ## Volume Maintenance
 
-Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3, or an NFS server. Saving to an object store is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.4.0/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is the endpoint used to access a backupstore in Longhorn. A backupstore is a NFS server or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.4.1/best-practices.md

@@ -94,7 +94,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li
 
 ## Volume Maintenance
 
-Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3, or an NFS server. Saving to an object store is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.4.1/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is the endpoint used to access a backupstore in Longhorn. A backupstore is a NFS server or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.4.2/best-practices.md

@@ -94,7 +94,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li
 
 ## Volume Maintenance
 
-Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3, or an NFS server. Saving to an object store is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.4.2/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is the endpoint used to access a backupstore in Longhorn. A backupstore is a NFS server or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.4.3/best-practices.md

@@ -94,7 +94,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li
 
 ## Volume Maintenance
 
-Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3, or an NFS server. Saving to an object store is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.4.3/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is the endpoint used to access a backupstore in Longhorn. A backupstore is a NFS server or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.4.4/best-practices.md

@@ -94,7 +94,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li
 
 ## Volume Maintenance
 
-Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3, or an NFS server. Saving to an object store is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.4.4/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is the endpoint used to access a backupstore in Longhorn. A backupstore is a NFS server or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.4.5/best-practices.md

@@ -94,7 +94,7 @@ If you're using `ext4` as the filesystem of the volume, we recommend adding a li
 
 ## Volume Maintenance
 
-Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3, or an NFS server. Saving to an object store is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.4.5/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is the endpoint used to access a backupstore in Longhorn. A backupstore is a NFS server or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.5.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
 
-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, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.5.0/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is an endpoint used to access a backup store in Longhorn. A backup store is an NFS server, SMB/CIFS server, Azure Blob Storage server, or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 or Azure is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS and SMB/CIFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.5.1/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
 
-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, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.5.1/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is an endpoint used to access a backup store in Longhorn. A backup store is an NFS server, SMB/CIFS server, Azure Blob Storage server, or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 or Azure is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS and SMB/CIFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.5.2/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
 
-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, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.5.2/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is an endpoint used to access a backup store in Longhorn. A backup store is an NFS server, SMB/CIFS server, Azure Blob Storage server, or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 or Azure is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS and SMB/CIFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)
 

content/docs/1.5.3/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
 
-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, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, which can complicate failover and upgrades.
+Using Longhorn's built-in backup feature is highly recommended. You can save backups to an object store such as S3 or to an NFS server. Saving to an object store is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 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.
 

content/docs/1.5.3/snapshots-and-backups/backup-and-restore/set-backup-target.md

@@ -5,7 +5,7 @@ weight: 1
 
 A backup target is an endpoint used to access a backup store in Longhorn. A backup store is an NFS server, SMB/CIFS server, Azure Blob Storage server, or S3 compatible server that stores the backups of Longhorn volumes. The backup target can be set at `Settings/General/BackupTarget`.
 
-Saving to an object store such as S3 or Azure is preferable, if possible, because it generally has better performance and reliability.  There is also the advantage of not having to mount and unmount the target, as for NFS and SMB/CIFS, which can complicate failover and upgrades.
+Saving to an object store such as S3 is preferable because it generally offers better performance and reliability.  Another advantage is that you do not need to mount and unmount the target, which can complicate failover and upgrades.
 
 For more information about how the backupstore works in Longhorn, see the [concepts section.](../../../concepts/#3-backups-and-secondary-storage)