Skip to content

fix: typo in publish-subscribe-semantics.md#5251

Open
kletnoe wants to merge 2 commits intoasyncapi:masterfrom
kletnoe:patch-1
Open

fix: typo in publish-subscribe-semantics.md#5251
kletnoe wants to merge 2 commits intoasyncapi:masterfrom
kletnoe:patch-1

Conversation

@kletnoe
Copy link
Copy Markdown

@kletnoe kletnoe commented Mar 18, 2026

Description

Summary by CodeRabbit

Documentation

  • Fixed a typo in the blog post documentation for improved clarity.

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 18, 2026

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 57e2d12
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/69c52931c55cf80008018d3c
😎 Deploy Preview https://deploy-preview-5251--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 18, 2026

📝 Walkthrough

Walkthrough

A typo correction in a blog post about pub-sub messaging semantics, changing "s messaging infrastructure" to "a messaging infrastructure" in a single sentence.

Changes

Cohort / File(s) Summary
Documentation Typo Fix
markdown/blog/publish-subscribe-semantics.md
Corrected article grammar by replacing "s messaging infrastructure" with "a messaging infrastructure".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A hop, a fix, a typo gone,
"An" where "s" had lingered long,
Grammar hops now bright and clear,
Publishing prose without a fear! 📝✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately describes the main change: fixing a typo in the publish-subscribe-semantics.md file, which matches the changeset summary.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can use oxc to improve the quality of JavaScript and TypeScript code reviews.

Add a configuration file to your project to customize how CodeRabbit runs oxc.

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (e106ba7) to head (57e2d12).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5251   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          830       830           
  Branches       159       159           
=========================================
  Hits           830       830           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
markdown/blog/publish-subscribe-semantics.md (1)

57-57: Consider hyphenating "event-driven" for grammatical correctness.

The phrase "event driven architecture" should use a hyphen when the compound adjective precedes the noun. As per static analysis tools, this improves grammatical correctness in technical documentation.

📝 Suggested grammar improvement
-In an event driven architecture there is no client/server paradigm. Applications do not directly communicate with one another - instead, each application sends and receives events via communication channels provided by a messaging infrastructure such as a broker. The broker ensures that events sent to a channel are delivered to interested applications. It can be considered *fire and forget* - an application sends an event, but does not have any interest in whether other applications receive or make use of the event.
+In an event-driven architecture there is no client/server paradigm. Applications do not directly communicate with one another - instead, each application sends and receives events via communication channels provided by a messaging infrastructure such as a broker. The broker ensures that events sent to a channel are delivered to interested applications. It can be considered *fire and forget* - an application sends an event, but does not have any interest in whether other applications receive or make use of the event.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@markdown/blog/publish-subscribe-semantics.md` at line 57, Replace the
unhyphenated adjective phrase "event driven architecture" with "event-driven
architecture" in the sentence that begins "In an event driven architecture..."
(the paragraph describing applications sending and receiving events via a
broker); also scan for any other occurrences of "event driven" in this document
and hyphenate them when used as a compound adjective to conform to grammar/style
guidance.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@markdown/blog/publish-subscribe-semantics.md`:
- Line 57: Replace the unhyphenated adjective phrase "event driven architecture"
with "event-driven architecture" in the sentence that begins "In an event driven
architecture..." (the paragraph describing applications sending and receiving
events via a broker); also scan for any other occurrences of "event driven" in
this document and hyphenate them when used as a compound adjective to conform to
grammar/style guidance.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5b196992-150b-4b69-aa11-508aa8c22e19

📥 Commits

Reviewing files that changed from the base of the PR and between 95e5f80 and 1633d46.

📒 Files selected for processing (1)
  • markdown/blog/publish-subscribe-semantics.md

@asyncapi-bot
Copy link
Copy Markdown
Contributor

asyncapi-bot commented Mar 18, 2026

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 42
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-5251--asyncapi-website.netlify.app/

Copy link
Copy Markdown
Member

@princerajpoot20 princerajpoot20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kletnoe please update the PR title according the convention mentioned by the BOT above. Also from next time, please preffer to open issue first, and not PR directly.

@thulieblack @TRohit20 PTAL

@kletnoe kletnoe changed the title Typo in publish-subscribe-semantics.md fix: typo in publish-subscribe-semantics.md Mar 22, 2026
@animeshk923
Copy link
Copy Markdown
Contributor

/rtm

@asyncapi-bot
Copy link
Copy Markdown
Contributor

Hello, @animeshk923! 👋🏼
This PR is not up to date with the base branch and can't be merged.
Please update your branch manually with the latest version of the base branch.
PRO-TIP: To request an update from the upstream branch, simply comment /u or /update and our bot will handle the update operation promptly.

       The only requirement for this to work is to enable [Allow edits from maintainers](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) option in your PR. Also the update will not work if your fork is located in an organization, not under your personal profile.
       Thanks 😄

@sonarqubecloud
Copy link
Copy Markdown

@animeshk923

This comment was marked as outdated.

@animeshk923
Copy link
Copy Markdown
Contributor

/au

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

Projects

Status: To Be Triaged

Development

Successfully merging this pull request may close these issues.

4 participants