refactor: docker build instruction line (README.md)

[Chayan8837]

Fix #3271
Description
Before

After

• fix the typing mistake in docker build instruction line there is a extra backtick at the end of code
• ...
• ...

Summary by CodeRabbit

Summary by CodeRabbit

• Documentation
  • Improved formatting and corrected a syntax error in the Docker build command in the README file.
  • Maintained the overall structure and content regarding project setup, requirements, and contribution guidelines.

[coderabbitai]

Walkthrough

The changes in the README.md file consist of a formatting correction in the Docker build command section. An extraneous backtick was removed to fix a syntax error. The document's overall structure, content, and instructions regarding project setup, requirements, and contribution guidelines remain unchanged.

Changes

File	Change Summary
README.md	Corrected syntax error in Docker build command; minor formatting adjustments.

Sequence Diagram(s)

No sequence diagram is generated as the changes are too simple and do not involve modifications to the control flow.

Assessment against linked issues

Objective	Addressed	Explanation
Correct the Docker build command syntax (#3271)	✅

Suggested labels

ready-to-merge

Suggested reviewers

• derberg
• magicmatatjahu
• Mayaleeeee
• asyncapi-bot-eve
• devilkiller-ag
• sambhavgupta0705
• akshatnema

🐰 "In the README, a change so slight,
A backtick's gone, now everything's right.
With setup and guidelines, clear as can be,
Hop along, dear coder, and build with glee!
Docker awaits, so let’s take flight,
With a click and a build, all will be bright!" 🌟

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0cc4490 and c45335d.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	c45335d
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/674ad7f7cf54640008e3b921
😎 Deploy Preview	https://deploy-preview-3272--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.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

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

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

[anshgoyalevil]

I always wanted to remove that extra backtick but was too lazy to create a PR. Thanks @Chayan8837

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.77%. Comparing base (eb9a128) to head (c45335d).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3272   +/-   ##
=======================================
  Coverage   67.77%   67.77%           
=======================================
  Files          21       21           
  Lines         664      664           
=======================================
  Hits          450      450           
  Misses        214      214           

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

[akshatnema]

/rtm