docs: protected mode is now enabled by-default

[efiop]

treeverse/dvc#3472

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.

🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.

Please chose to allow us to edit your branch when creating the PR.

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

[jorgeorpinel]

Good stuff. Some comments below. We can take it over at some point if needed, up to you guys 🙂

[efiop]

Will take a fresh look in the morning. Thanks for the reviews! @jorgeorpinel 🙏

[jorgeorpinel]

Thank you! Only my comments on public/static/docs/user-guide/large-dataset-optimization.md are pending now, it seems.

[efiop]

@jorgeorpinel Addressed all of your comments, please take a look when you'll have time. Thanks!

[jorgeorpinel]

A couple more details. Let me try to commit the suggestions myself here on GH 😬

[jorgeorpinel]

Suggested change

	protect against that, DVC makes hard/soft links read-only, forcing the user to
	use `dvc unprotect` before modifying them. Finally, a 4th "linking" alternative
	protect against that, DVC makes hardlinks and symlinks links read-only, which requires the user to
	use `dvc unprotect` before modifying them.
	Finally, a 4th "linking" alternative

Needs rewrap... Let's see if Restyled can fix this ⏳

[jorgeorpinel]

Strange. No Restyled difference 🙁

[jorgeorpinel]

Done Ruslan! But there's a formatting check failing and Restyled isn't fixing it? See #1058 (comment)

[efiop]

@jorgeorpinel Maybe it is not configured right, I haven't looked deeply in our dvc.org setup. Fixed manually.

[shcheklein]

Cool stuff, thanks @efiop and @jorgeorpinel !