chore: typo on developer guide

[zhravan]

Summary by CodeRabbit

• Documentation
  • Corrected a typographical error in the contributing guide.

[vercel]

@Shravan20 is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

A typographical error in the contributing guide was corrected, changing "Deleoper" to "Developer" in a link referencing the development environment documentation. No other changes were made.

Changes

File(s)	Change Summary
pages/contributing.mdx	Fixed typo: "Deleoper" → "Developer" in link text.

Poem

A typo hopped into our guide,
But now it’s gone, no need to hide!
"Developer" stands proud and clear,
The path for helpers far and near.
With every fix, our docs grow bright—
Thanks for keeping words just right!
🐰✨

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

pages/contributing.mdx (1)

60-62: Consider normalising the ordered-list numbering.
Steps jump from 3. → 6. → 7. → 9. → 10.. GitHub Markdown preserves the literal numbers, so readers will see the discontinuity. Either make every item 1. (GitHub auto-increments) or renumber sequentially.

Example quick fix:

-6. **Make your changes**: Implement the changes you wish to contribute.
-7. **Push your changes**: Push your changes to your fork.
-9. **Create a pull request**: Create an draft pull request with the name of the feature.
-10. **Test your changes**: (OPTIONAL, only for big changes)
+4. **Make your changes**: Implement the changes you wish to contribute.
+5. **Push your changes**: Push your changes to your fork.
+6. **Create a pull request**: Create a draft pull request with the name of the feature.
+7. **Test your changes**: (OPTIONAL, only for big changes)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dc83efd and a472631.

📒 Files selected for processing (1)

• pages/contributing.mdx (1 hunks)

🔇 Additional comments (1)

pages/contributing.mdx (1)

61-61: Typo correction acknowledged – good catch.
The change from “Deleoper” to “Developer” fixes the broken anchor text. No further action needed.