Update cursor-rules.mdc to fix unbalanced backticks

[joedevon]

You had 2 opening backticks without closing the outer set.

For nested backticks, you use 4 on the outer set. See: https://python-markdown.github.io/extensions/fenced_code_blocks/

Not a biggie but just a little less thinking for Cursor to do if it's formatted correctly.

Summary by CodeRabbit

• Style
  • Improved the presentation of code blocks in documentation for enhanced readability.
  • Ensured proper formatting with a consistent structure across the document.

[vercel]

@joedevon is attempting to deploy a commit to the Inbox Zero Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

The markdown file .cursor/rules/cursor-rules.mdc has been updated to adjust the formatting of code block delimiters. The document now uses double backticks for both opening and closing code blocks instead of a single backtick. Additionally, a newline has been added at the end of the file. There were no changes to exported or public entity declarations.

Changes

File	Change Summary
.cursor/rules/cursor-rules.mdc	Updated code block delimiters from single backticks to double backticks; appended a newline at end

Poem

I'm just a rabbit with a coding beat,
Hopping along as formatting gets neat.
Double backticks now light the way,
A newline wiggles at the end of day.
With whiskers twitching, I celebrate this treat!
🐰✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eae229d and e3bd262.

📒 Files selected for processing (1)

• .cursor/rules/cursor-rules.mdc (2 hunks)

🔇 Additional comments (2)

.cursor/rules/cursor-rules.mdc (2)

40-41: Balanced Outer Fence Introduced for Nested Code Blocks
The change correctly replaces the insufficient fence delimiter with a four-backtick sequence, ensuring that the outer block properly encloses the nested code block (which uses triple backticks). This implementation now adheres to the Markdown guidelines for nested fences and should resolve issues with unbalanced backticks.

---

65-67: Consistent and Correct Closing Delimiter
The updated closing fence (four backticks) now matches the opening fence, ensuring that the outer code block is properly terminated. Additionally, the added newline at the end of the file is a good practice for UNIX compatibility and file formatting.

---

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

• 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[elie222]

Thanks for the contribution!
And good to learn about 4 backticks!