diff --git a/public/static/docs/command-reference/config.md b/public/static/docs/command-reference/config.md
index cd58941a59..fa526efe14 100644
--- a/public/static/docs/command-reference/config.md
+++ b/public/static/docs/command-reference/config.md
@@ -127,9 +127,9 @@ for more details.) This section contains the following options:
   to protect user from accidental cache and repository corruption.
 
   ⚠️ If you manually set `cache.type` to `hardlink` or `symlink`, **you will
-  corrupt the cache** if you modify tracked data files in the workspace. In
-  an attempt to prevent that, DVC will automatically protect those file links
-  (make them read-only). Use `dvc unprotect` to be able to modify them safely.
+  corrupt the cache** if you modify tracked data files in the workspace. In an
+  attempt to prevent that, DVC will automatically protect those file links (make
+  them read-only). Use `dvc unprotect` to be able to modify them safely.
 
   There are pros and cons to different link types. Refer to
   [File link types](/doc/user-guide/large-dataset-optimization#file-link-types-for-the-dvc-cache)
diff --git a/public/static/docs/user-guide/large-dataset-optimization.md b/public/static/docs/user-guide/large-dataset-optimization.md
index 5c965b574c..ffba28f2ef 100644
--- a/public/static/docs/user-guide/large-dataset-optimization.md
+++ b/public/static/docs/user-guide/large-dataset-optimization.md
@@ -114,8 +114,8 @@ $ dvc config cache.type hardlink,symlink
 
 > Refer to `dvc config cache` for more details.
 
-Note that your workspace files will be in read-only mode because of the efforts
-to protect cache from corruption. Please refer to the
+Note that with this `cache.type`, your workspace files will be in read-only mode
+in order to protect the cache from corruption. Please refer to the
 [Update a Tracked File](/doc/user-guide/updating-tracked-files) on how to manage
 tracked files under these cache configurations.