Closed bandantonio closed 3 weeks ago
The changes across multiple markdown documents focus on enhancing clarity, consistency, and readability of the content related to AsyncAPI concepts. Key terms are emphasized, sentence structures are refined, and descriptions are streamlined to improve the overall flow of information. Specific adjustments include rephrasing definitions, clarifying roles and relationships within Event-Driven Architecture, and ensuring consistent terminology throughout the documents. Diagrams and their descriptions have also been updated for better comprehension.
File Path | Change Summary |
---|---|
markdown/docs/concepts/application.md | Rephrased for clarity; emphasized "application" in italics; modified definitions and examples for readability. |
markdown/docs/concepts/asyncapi-document/index.md | Textual modifications for clarity; adjusted phrases for grammatical consistency and improved readability. |
markdown/docs/concepts/channel.md | Enhanced clarity and consistency; rephrased definitions and descriptions; emphasized "channel" in italics. |
markdown/docs/concepts/consumer.md | Clarified descriptions of consumers; emphasized asynchronous behavior; updated diagram descriptions for consistency. |
markdown/docs/concepts/index.md | Simplified section header and introductory text for clarity. |
markdown/docs/concepts/message.md | Enhanced clarity and readability; streamlined definitions and descriptions; rephrased comparisons between messages and events. |
markdown/docs/concepts/producer.md | Improved clarity and consistency; refined definitions and examples; restructured explanations of the publish/subscribe model. |
markdown/docs/concepts/protocol.md | Enhanced clarity; restructured descriptions of protocols; updated terminology for formality. |
markdown/docs/concepts/server.md | Clarified server roles and interactions; emphasized messaging broker functions; improved descriptions of architecture. |
autoapproved
, autoupdate
🐰 In the garden where knowledge grows,
Clarity blooms, and understanding flows.
With words refined and meanings clear,
We hop along, spreading cheer!
Through channels and messages, we play,
In the world of AsyncAPI, we find our way! 🌼
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Built without sensitive environment variables
Name | Link |
---|---|
Latest commit | a13e3ce1ce8cb8e2d6a86f2ab7f2d19e21408028 |
Latest deploy log | https://app.netlify.com/sites/asyncapi-website/deploys/672bdfb290b284000845af8e |
Deploy Preview | https://deploy-preview-3354--asyncapi-website.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 49.14%. Comparing base (
2fb1634
) to head (a13e3ce
). Report is 1 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
⚡️ Lighthouse report for the changes in this PR: | Category | Score |
---|---|---|
🔴 Performance | 44 | |
🟢 Accessibility | 98 | |
🟢 Best practices | 92 | |
🟢 SEO | 100 | |
🔴 PWA | 33 |
Lighthouse ran on https://deploy-preview-3354--asyncapi-website.netlify.app/
@bandantonio Are these changes made in consideration with @quetzalliwrites? I don't find any concerned issue linked with this PR.
@akshatnema Sure, this was discussed with @quetzalliwrites some time ago. I pinged her again, so we could probably create an 'epic' issue for that so I can take care of all the related styling aspects across the docs.
Hola @akshatnema, thanks for looping me in! 😸 Yes, the good news it that Anthony had already talked to me about his suggestions offline. (I still need to review this PR and see if I agree tehehe)
Ah, @bandantonio, to Akshat's point, would you mind creating a new docs issue for your proposal to link to this PR? He makes a good point that a change proposed like this one needs a docs issue.
Description This PR improves writing style of the documents located in the Concepts section.
Motivation: make writing more consistent and predictable, as well as easier to skim and understand.
Fixes #3374
Summary by CodeRabbit