diff --git a/content/docs/1.5.0/references/settings.md b/content/docs/1.5.0/references/settings.md
index 3b562c911..483813192 100644
--- a/content/docs/1.5.0/references/settings.md
+++ b/content/docs/1.5.0/references/settings.md
@@ -109,7 +109,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../advanced-resources/rwx-workloads).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.5.1/references/settings.md b/content/docs/1.5.1/references/settings.md
index 3b562c911..483813192 100644
--- a/content/docs/1.5.1/references/settings.md
+++ b/content/docs/1.5.1/references/settings.md
@@ -109,7 +109,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../advanced-resources/rwx-workloads).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.5.2/references/settings.md b/content/docs/1.5.2/references/settings.md
index 11fda9c48..5d768f1d6 100644
--- a/content/docs/1.5.2/references/settings.md
+++ b/content/docs/1.5.2/references/settings.md
@@ -109,7 +109,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../advanced-resources/rwx-workloads).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.5.3/references/settings.md b/content/docs/1.5.3/references/settings.md
index 11fda9c48..5d768f1d6 100644
--- a/content/docs/1.5.3/references/settings.md
+++ b/content/docs/1.5.3/references/settings.md
@@ -109,7 +109,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../advanced-resources/rwx-workloads).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.5.4/references/settings.md b/content/docs/1.5.4/references/settings.md
index d26e6b10e..298d7635f 100644
--- a/content/docs/1.5.4/references/settings.md
+++ b/content/docs/1.5.4/references/settings.md
@@ -123,7 +123,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../advanced-resources/rwx-workloads).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.5.5/references/settings.md b/content/docs/1.5.5/references/settings.md
index d26e6b10e..298d7635f 100644
--- a/content/docs/1.5.5/references/settings.md
+++ b/content/docs/1.5.5/references/settings.md
@@ -123,7 +123,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../advanced-resources/rwx-workloads).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.5.6/references/settings.md b/content/docs/1.5.6/references/settings.md
index f46271fb8..3e4dd0995 100644
--- a/content/docs/1.5.6/references/settings.md
+++ b/content/docs/1.5.6/references/settings.md
@@ -124,7 +124,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../advanced-resources/rwx-workloads).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.6.0/references/settings.md b/content/docs/1.6.0/references/settings.md
index c9c1a544f..9c7417698 100644
--- a/content/docs/1.6.0/references/settings.md
+++ b/content/docs/1.6.0/references/settings.md
@@ -146,7 +146,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../nodes-and-volumes/volumes/rwx-volumes).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.6.1/references/settings.md b/content/docs/1.6.1/references/settings.md
index c9c1a544f..9c7417698 100644
--- a/content/docs/1.6.1/references/settings.md
+++ b/content/docs/1.6.1/references/settings.md
@@ -146,7 +146,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../nodes-and-volumes/volumes/rwx-volumes).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.6.2/references/settings.md b/content/docs/1.6.2/references/settings.md
index c9c1a544f..9c7417698 100644
--- a/content/docs/1.6.2/references/settings.md
+++ b/content/docs/1.6.2/references/settings.md
@@ -146,7 +146,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../nodes-and-volumes/volumes/rwx-volumes).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.6.3/references/settings.md b/content/docs/1.6.3/references/settings.md
index ab6a0afd2..1250057e2 100644
--- a/content/docs/1.6.3/references/settings.md
+++ b/content/docs/1.6.3/references/settings.md
@@ -147,7 +147,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - The volumes used by workloads are RWX, because the Longhorn share manager, which provides the RWX NFS service, has its own resilience mechanism to ensure availability until the volume gets reattached without relying on the pod lifecycle to trigger volume reattachment. For details, see [here](../../nodes-and-volumes/volumes/rwx-volumes).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.7.0/references/settings.md b/content/docs/1.7.0/references/settings.md
index ae9813a64..bd77fdbce 100644
--- a/content/docs/1.7.0/references/settings.md
+++ b/content/docs/1.7.0/references/settings.md
@@ -154,7 +154,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - Workload pods with *cluster network* RWX volumes. The setting does not apply to such pods because the Longhorn Share Manager, which provides the RWX NFS service, has its own resilience mechanism. This mechanism ensures availability until the volume is reattached without relying on the pod lifecycle to trigger volume reattachment. The setting does apply, however, to workload pods with *storage network* RWX volumes. For more information, see [ReadWriteMany (RWX) Volume](../../nodes-and-volumes/volumes/rwx-volumes) and [Storage Network](../../advanced-resources/deploy/storage-network#limitation).
 
 #### Automatic Salvage
 
diff --git a/content/docs/1.7.1/references/settings.md b/content/docs/1.7.1/references/settings.md
index 8f7391b16..55fd1f58d 100644
--- a/content/docs/1.7.1/references/settings.md
+++ b/content/docs/1.7.1/references/settings.md
@@ -154,7 +154,6 @@ If disabled, Longhorn will not delete the workload pod that is managed by a cont
 
 > **Note:** This setting doesn't apply to below cases.
 > - The workload pods don't have a controller; Longhorn never deletes them.
-> - Workload pods with *cluster network* RWX volumes. The setting does not apply to such pods because the Longhorn Share Manager, which provides the RWX NFS service, has its own resilience mechanism. This mechanism ensures availability until the volume is reattached without relying on the pod lifecycle to trigger volume reattachment. The setting does apply, however, to workload pods with *storage network* RWX volumes. For more information, see [ReadWriteMany (RWX) Volume](../../nodes-and-volumes/volumes/rwx-volumes) and [Storage Network](../../advanced-resources/deploy/storage-network#limitation).
 
 #### Automatic Salvage