Fix broken links and flow #254
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
joseph-henry
requested review from
laduke,
danitheturtle,
rcoder,
glimberg,
aaronjohnson,
constantijn,
rokjoana and
a team
as code owners
|
@joseph-henry looks like the linter failed |
|
Really strange, the linter on my machine cannot detect that last misspelling that the GH runner can, but it did properly detect the exact same word misspelled elsewhere in the file. |
laduke
approved these changes
May 8, 2025
|
I wish the spell checker was better somehow. I'm not sure how. There are lots of special words in technical sites like this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch fixes a bunch of broken links to
slugs, markdown files, and page anchors. It fleshes out a few key areas in certain articles, improves user flow a bit, and introduces a glossary.md that we should all work on filling out. This is just a first step before a more comprehensive reorganization.I've identified many more areas where a search will yield a sub-optimal result (either a useless mention, or a confusing/inappropriately-scoped article, or even duplicate discussions of the same feature). This PR does not address these issues but makes it a bit easier to do so later.