chore(architecture): improve architecture page wording & readability based on scores - #720
Open
stijnmoreels wants to merge 4 commits into
Open
chore(architecture): improve architecture page wording & readability based on scores#720stijnmoreels wants to merge 4 commits into
stijnmoreels wants to merge 4 commits into
Conversation
✅ Deploy Preview for invictus-for-azure ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
stijnmoreels
marked this pull request as ready for review
September 3, 2026 06:52
stijnmoreels
requested review from
GoutsmitSam and
pim-simons
as code owners
September 3, 2026 06:52
pim-simons
requested changes
Sep 3, 2026
Co-authored-by: Pim Simons <32359437+pim-simons@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Improves the wording of the architecture page to use 'diagnostic data' instead of 'flow trace'. It removes the need for extra terms, while reusing Azure wording.