Fixed vale errors

[eshanrnh]

📋 Description

While doing the spell check test, the report generated different validation errors. Fixed these, except for the Sentence length (fix) errors.

• Brands
• Terms
• Acronyms
• Spelling
• Editorializing
• Repetition
• Link Text Clarity
• Names
• Spacing

📎 Related Issues (if applicable)

NA

✅ Contributor Checklist

I've followed the Umbraco Documentation Style Guide and can confirm that:

• Code blocks are correctly formatted.
• Sentences are short and clear (preferably under 25 words).
• Passive voice and first-person language (“we”, “I”) are avoided.
• Relevant pages are linked.
• All links work and point to the correct resources.
• Screenshots or diagrams are included if useful.
• Any code examples or instructions have been tested.
• Typos, broken links, and broken images are fixed.

Product & Version (if relevant)

Cloud

Deadline (if relevant)

Can merge this if/after the spell check rule is in place.

📚 Helpful Resources

• 🧾 Umbraco Contribution Guidelines
• ✍️ Umbraco Documentation Style Guide

[github-actions]

The Link Checker found broken links in your PR.
Please review the following list:

Broken links found in:
umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content/README.md

⚓ Anchor not found → umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content#partial-restore | Cannot find fragment

⚓ Anchor not found → umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content#restore-when-starting-up-the-project-locally | Cannot find fragment

⚓ Anchor not found → umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content#tree-restore | Cannot find fragment

⚓ Anchor not found → umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content#workspace-restore | Cannot find fragment

Broken links found in:
umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md

⚓ Anchor not found → umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security#cookies-and-security | Cannot find fragment

⚓ Anchor not found → umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security#restrict-backoffice-access-using-ip-filtering | Cannot find fragment

⚓ Anchor not found → umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/product-upgrades#the-process-of-auto-upgrading-a-umbraco-cloud-project | Cannot find fragment

Broken links found in:
umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation.md

⚓ Anchor not found → umbraco-cloud/go-live/manage-hostnames/security-certificates | Cannot find file

Broken links found in:
umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes/README.md

⚓ Anchor not found → umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes#deploy-hotfix-with-git-branching | Cannot find fragment

⚓ Anchor not found → umbraco-cloud/optimize-and-maintain-your-site/manage-product-upgrades/hotfixes#move-files-manually | Cannot find fragment

Broken links found in:
umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/resolve-issues-quickly-and-efficiently/deployments/structure-error.md

⚓ Anchor not found → umbraco-cloud/build-and-customize-your-solution/set-up-your-project/databases/cloud-database#connecting-to-your-cloud-database-locally | Cannot find fragment

Broken links found in:
umbraco-cloud/release-notes/archive/overview-2022/README.md

⚓ Anchor not found → umbraco-cloud/release-notes/archive/overview-2022#february-2022 | Cannot find fragment

Broken links found in:
umbraco-cloud/release-notes/archive/overview-2024/2024-07-releasenotes.md

⚠ Unknown error → [999] https://www.linkedin.com/in/joshua-nibbs/ |#124; Rejected status code (this depends on your "accept" configuration): Unknown status codeFull Github Actions output

[eshanrnh]

@sofietoft, Should we also bold Broken links found in: in the Link checker.yml? Since it's clearly lost/difficult to read when there are multiple files listed.