Fix typo

Signed-off-by: Derek Su <[email protected]>
longhorn · Oct 4, 2023 · 9f371ad · 9f371ad
1 parent d10ab8f
commit 9f371ad
Show file tree

Hide file tree

Showing 15 changed files with 15 additions and 15 deletions.
diff --git a/content/docs/1.4.0/references/storage-class-parameters.md b/content/docs/1.4.0/references/storage-class-parameters.md
@@ -114,7 +114,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.4.1/references/storage-class-parameters.md b/content/docs/1.4.1/references/storage-class-parameters.md
@@ -114,7 +114,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.4.2/references/storage-class-parameters.md b/content/docs/1.4.2/references/storage-class-parameters.md
@@ -114,7 +114,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.4.3/references/storage-class-parameters.md b/content/docs/1.4.3/references/storage-class-parameters.md
@@ -114,7 +114,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.4.4/references/storage-class-parameters.md b/content/docs/1.4.4/references/storage-class-parameters.md
@@ -114,7 +114,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.5.0/deploy/important-notes/index.md b/content/docs/1.5.0/deploy/important-notes/index.md
@@ -86,7 +86,7 @@ Please use the new setting [Node Drain Policy](../../references/settings#node-dr
 
 ### Instance Managers Consolidated
 
-Engine instance mangers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
+Engine instance managers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
 
 The `Guaranteed Engine Manager CPU` and `Guaranteed Replica Manager CPU` settings are removed and replaced by `Guaranteed Instance Manager CPU`.
 

diff --git a/content/docs/1.5.0/references/storage-class-parameters.md b/content/docs/1.5.0/references/storage-class-parameters.md
@@ -115,7 +115,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.5.1/deploy/important-notes/index.md b/content/docs/1.5.1/deploy/important-notes/index.md
@@ -86,7 +86,7 @@ Please use the new setting [Node Drain Policy](../../references/settings#node-dr
 
 ### Instance Managers Consolidated
 
-Engine instance mangers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
+Engine instance managers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
 
 The `Guaranteed Engine Manager CPU` and `Guaranteed Replica Manager CPU` settings are removed and replaced by `Guaranteed Instance Manager CPU`.
 

diff --git a/content/docs/1.5.1/references/storage-class-parameters.md b/content/docs/1.5.1/references/storage-class-parameters.md
@@ -115,7 +115,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.5.2/deploy/important-notes/index.md b/content/docs/1.5.2/deploy/important-notes/index.md
@@ -97,7 +97,7 @@ Please use the new setting [Node Drain Policy](../../references/settings#node-dr
 
 ### Instance Managers Consolidated
 
-Engine instance mangers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
+Engine instance managers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
 
 The `Guaranteed Engine Manager CPU` and `Guaranteed Replica Manager CPU` settings are removed and replaced by `Guaranteed Instance Manager CPU`.
 

diff --git a/content/docs/1.5.2/references/storage-class-parameters.md b/content/docs/1.5.2/references/storage-class-parameters.md
@@ -115,7 +115,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/content/docs/1.6.0/deploy/important-notes/index.md b/content/docs/1.6.0/deploy/important-notes/index.md
@@ -97,7 +97,7 @@ Please use the new setting [Node Drain Policy](../../references/settings#node-dr
 
 ### Instance Managers Consolidated
 
-Engine instance mangers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
+Engine instance managers and replica instance managers has been consolidated. Previous engine/replica instance managers are now deprecated, but they will still provide service to the existing attached volumes.
 
 The `Guaranteed Engine Manager CPU` and `Guaranteed Replica Manager CPU` settings are removed and replaced by `Guaranteed Instance Manager CPU`.
 

diff --git a/content/docs/1.6.0/references/storage-class-parameters.md b/content/docs/1.6.0/references/storage-class-parameters.md
@@ -116,7 +116,7 @@ If enabled, try to keep the data on the same node as the workload for better per
   - If "strict-local" is not possible for whatever other reason, volume creation will be failed.  A "strict-local" replica that becomes displaced from its workload will be marked as "Stopped".  
 
 >  Global setting: [Default Data Locality](../settings#default-data-locality)  
->  More defails in [Data Locality](../../high-availability/data-locality).
+>  More details in [Data Locality](../../high-availability/data-locality).
 
 #### Replica Auto-Balance *(field: `parameters.replicaAutoBalance`)*
 > Default: `ignored`  

diff --git a/...archives/0.8.0/users-guide/backup-and-restore/backupstores-and-backuptargets.md b/...archives/0.8.0/users-guide/backup-and-restore/backupstores-and-backuptargets.md
@@ -83,7 +83,7 @@ Now set `Settings/General/BackupTarget` to
 ```
 s3://backupbucket@us-east-1/
 ```
-And `Setttings/General/BackupTargetSecret` to
+And `Settings/General/BackupTargetSecret` to
 ```
 minio-secret
 ```

diff --git a/content/kb/space-consumption-guideline.md b/content/kb/space-consumption-guideline.md
@@ -34,5 +34,5 @@ In this case, the node is probably marked as NotReady due to the disk pressure.
 To do recover nodes and disk, we would recommend directly removing some redundant replica directories for the full disk. Here redundant replicas means that the corresponding volumes have healthy replicas in other disks. Later on Longhorn will automatically rebuild new replicas in other disks if possible.
 Besides, users may need to expand the existing disks or add more disks to avoid future disk exhaustion issues.
 
-Notice that the disk exhausion may be caused by replicas being unevenly scheduled. Users can check [setting Replica Auto Balance](../../docs/1.5.1/high-availability/auto-balance-replicas) for this scenario.
+Notice that the disk exhaustion may be caused by replicas being unevenly scheduled. Users can check [setting Replica Auto Balance](../../docs/1.5.1/high-availability/auto-balance-replicas) for this scenario.