Skip to content

docs: correct the message-handler guide's link label - #4981

Open
vaibhav8a wants to merge 1 commit into
AxonIQ:mainfrom
vaibhav8a:fix-guide-link-label
Open

docs: correct the message-handler guide's link label#4981
vaibhav8a wants to merge 1 commit into
AxonIQ:mainfrom
vaibhav8a:fix-guide-link-label

Conversation

@vaibhav8a

Copy link
Copy Markdown

docs/README.md:15 labels the guide \./message-handler-tunning-guide/`while linking tomessage-handler-customization-guide`.

Two things are off: tunning is misspelled, and more importantly the label names a directory that does not exist — the guide is message-handler-customization-guide, which is what the link target and the docs.axoniq.io URL on the same line both use.

Every sibling entry keeps label and target identical (\./identifier-generation-guide/`](identifier-generation-guide), `./meta-annotations-guide/`](meta-annotations-guide)`), so this one is the outlier. Corrected the label to match its target rather than only fixing the spelling.

@vaibhav8a
vaibhav8a requested a review from a team as a code owner August 26, 2026 12:38
@vaibhav8a
vaibhav8a requested review from MateuszNaKodach, jangalinski and laura-devriendt-lemon and removed request for a team August 26, 2026 12:38
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@smcvb smcvb added Type: Bug Use to signal issues that describe a bug within the system. Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Documentation Use to signal issues that describe documentation work. labels Aug 26, 2026
@smcvb smcvb added this to the Release 5.4.0 milestone Aug 26, 2026
@smcvb

smcvb commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@vaibhav8a, first and foremost, thanks for contributing!
I do need to ask though: can you sign the CLA? Without that, I am afraid I cannot merge this changes in.
The CLA is in place to protect both you and us against minor legal concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Bug Use to signal issues that describe a bug within the system. Type: Documentation Use to signal issues that describe documentation work.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants