docs: update reactive messaging (backport #2537)

[mergify]

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

• Documentation content changes

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

Other information

Internal Issue (If applicable):

---

This is an automatic backport of pull request #2537 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 1119f29 has failed:

On branch mergify/bp/release/stable/4.2/pr-2537
Your branch is up to date with 'origin/release/stable/4.2'.

You are currently cherry-picking commit 1119f2971.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   doc/Learn/Mvux/Advanced/Messaging.md

no changes added to commit (use "git add" and/or "git commit -a")

Cherry-pick of c91ab75 has failed:

On branch mergify/bp/release/stable/4.2/pr-2537
Your branch is ahead of 'origin/release/stable/4.2' by 3 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit c91ab7583.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   doc/Learn/Mvux/Advanced/Messaging.md

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[kazo0]

@ajpinedam there seems to be some merge conflicts for this docs backport, could you take a look to resolve them?

[ajpinedam]

@ajpinedam there seems to be some merge conflicts for this docs backport, could you take a look to resolve them?

@kazo0 Fixed