Remove mentions of Azure and CIFS backupstore targets in v1.4.x docs.

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 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 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.
 
 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/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 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 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.
 
 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/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 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 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.
 
 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/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 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 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.
 
 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/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 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 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.
 
 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/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 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 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.
 
 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.