Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typo fix README.md #4034

Open
wants to merge 1 commit into
base: stage
Choose a base branch
from
Open

Conversation

MonkeyKing44
Copy link

Pull Request Title

Fix Typo in README.md


Description

This pull request fixes a typo in the README.md file located at packages/server/src/queries/complex/.

  • Original: recommeneded
  • Corrected: recommended

Copy link

vercel bot commented Jan 23, 2025

@MonkeyKing44 is attempting to deploy a commit to the OsmoLabs Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Jan 23, 2025

Walkthrough

The pull request contains a minor documentation update in the README file for complex queries. The change involves correcting a typographical error, changing "it is recommened" to "it is recommended" in the documentation. This is a simple spelling correction that does not impact the code's functionality or behavior.

Changes

File Change Summary
packages/server/src/queries/complex/README.md Corrected spelling from "recommened" to "recommended"

Note: This change is purely a documentation improvement with no functional impact on the codebase.


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
🪧 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.

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.

Copy link
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.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/server/src/queries/complex/README.md (1)

60-60: Consider using "among" instead of "amongst".

While both prepositions are correct, "among" is more commonly used in modern writing and would maintain a more contemporary style in the documentation.

-If values will not exceed 1MB and are especially expensive to query or calculate, the `RemoteCache` can be used. This will be shared amongst all server runtimes.
+If values will not exceed 1MB and are especially expensive to query or calculate, the `RemoteCache` can be used. This will be shared among all server runtimes.
🧰 Tools
🪛 LanguageTool

[style] ~60-~60: The preposition ‘amongst’ is correct, but some people think that it is old-fashioned or literary. A more frequently used alternative is the preposition “among”.
Context: ...Cache` can be used. This will be shared amongst all server runtimes. Due to networking ...

(AMONGST)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 348b889 and b5636ae.

📒 Files selected for processing (1)
  • packages/server/src/queries/complex/README.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
packages/server/src/queries/complex/README.md

[style] ~60-~60: The preposition ‘amongst’ is correct, but some people think that it is old-fashioned or literary. A more frequently used alternative is the preposition “among”.
Context: ...Cache` can be used. This will be shared amongst all server runtimes. Due to networking ...

(AMONGST)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Summary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant