Fix table of contents links in scenarios.md #7592
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
busrasengul
reviewed
Nov 6, 2025
Contributor
busrasengul
left a comment
busrasengul
left a comment
There was a problem hiding this comment.
Looks good to me!
Thank you @NikRimington <3
eshanrnh
approved these changes
Nov 6, 2025
Contributor
There was a problem hiding this comment.
Thanks for the PR, @NikRimington 🙌 The PR looks great.
I noticed a small typo for which I have added a suggestion. I'll take care of it 💪
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📋 Description
The in page table of contents had incorrect links to navigate down the page. Where ever there was an & in the name it was doing
--instead of-and-.✅ 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.Screenshots or diagrams are included if useful.Any code examples or instructions have been tested.