Update Longhorn Readme

Author: YuryHrytsuk

charts/longhorn/README.md

@@ -1,30 +1,32 @@
 # Longhorn (LH) Knowledge Base
 
-### Can LH be used for critical services (e.g. Database)
+### Can LH be used for critical services (e.g., Databases)?
 
-As of now we shall avoid using LH for critical services. Instead we should refer to a more reliable and easy-to-maintain solution (e.g. Application-Level replication [Postgres Operators], S3, ...)
+As of now, we should avoid using LH for critical services. Instead, we should rely on more reliable and easier-to-maintain solutions (e.g., application-level replication [Postgres Operators], S3, etc.).
 
-LH is using networking for keeping replicas in sync and IO-heavy workloads may overload it easily leading to unpredictable consequances. Before we manage to extensively monitor LH and scale properly on demand, we shall not use it for critical services or IO-heave services
+LH uses networking to keep replicas in sync, and IO-heavy workloads may easily overload it, leading to unpredictable consequences. Until we can extensively monitor LH and scale it properly on demand, it should not be used for critical or IO-heavy services.
 
-### How does LH decide which node's disk to use as storage
+### How does LH decide which node's disk to use as storage?
 
-It depends on configuration. There are 3 possibilities:
+It depends on the configuration. There are three possibilities:
 * https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/
 
-As long as we use `Create Default Disk on Labeled Nodes` it relies on `node.longhorn.io/create-default-disk` kubernetes node's label
+When using the `Create Default Disk on Labeled Nodes` option, it relies on the `node.longhorn.io/create-default-disk` Kubernetes node label.
 
 Source: https://longhorn.io/docs/1.8.1/nodes-and-volumes/nodes/default-disk-and-node-config/#customizing-default-disks-for-new-nodes
 
-### Will LH pick up storage from a newly-added node
+### Will LH pick up storage from a newly added node?
 
-By default LH will use storage on all (newly created as well) Nodes where it runs. If `createDefaultDiskLabeledNodes` is configured, then it depends on label of the node
+By default, LH will use storage on all nodes (including newly created ones) where it runs. If `createDefaultDiskLabeledNodes` is configured, it will depend on the label of the node.
 
 Source:
 * https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/
 * https://longhorn.io/docs/1.8.1/nodes-and-volumes/nodes/default-disk-and-node-config/#customizing-default-disks-for-new-nodes
 
-### Can workloads be run on nodes where there is no LH
+### Can workloads be run on nodes where LH is not installed?
 
-They can as long as LH is not bound to specific nodes via `nodeSelector` or `systemManagedComponentsNodeSelector` settings. If LH is configure to run on specific nodes, then workloads can only be run on these nodes only.
+Workloads can run on nodes without LH as long as LH is not restricted to specific nodes via the `nodeSelector` or `systemManagedComponentsNodeSelector` settings. If LH is configured to run on specific nodes, workloads can only run on those nodes.
+
+Note: There is an [ongoing bug](https://github.com/longhorn/longhorn/discussions/7312#discussioncomment-13030581) where LH will raise warnings when workloads run on nodes without LH. However, it will still function correctly.
 
 Source: https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/