Fix GitHub Markdown compatibility for notes

[cyte-zhang]

docs: Replace unsupported :::note syntax with GitHub-compatible Markdown

Description

This PR replaces unsupported :::note syntax with GitHub-compatible Markdown to improve rendering on GitHub. Specifically:

• Converted :::note blocks into blockquotes (>) for better readability.

---

Before

After

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces documentation formatting changes in the Cosmos SDK beginner's guide, specifically in the "00-app-anatomy.md" file. The modifications involve updating the documentation's visual presentation by replacing the original block notation (:::note) with a more modern markdown block quote format (> **Synopsis**). These changes aim to improve the readability and consistency of the documentation while preserving the original content about Cosmos SDK application anatomy.

Changes

File	Change Summary
docs/learn/beginner/00-app-anatomy.md	Updated documentation formatting from block notation to markdown block quote for synopsis and note sections

Suggested labels

T:Docs

Suggested reviewers

• akhilkumarpilli
• lucaslopezf
• testinginprod

Possibly related PRs

• docs(x/epochs): fix note box display failure #21644: Formatting adjustments in Markdown documentation
• docs: fix typos in documentation files #23063: Addressing typographical errors in documentation files
• docs: fix typos #23152: Fixing typos in documentation
• docs: add a synopsis upgrade doc for 52 #23097: Adding a new upgrade guide to improve documentation

---

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f9bb180 and f0b3769.

📒 Files selected for processing (1)

• docs/learn/beginner/00-app-anatomy.md (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• docs/learn/beginner/00-app-anatomy.md

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Summary

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[aljo242]

We use a specific rendering engine for our docs to display. Closing as this does not follow our CONTRIBUTING guidelines