README Typos: Correct "Ommitting" and "exetutables" to "Omitting and executables"

[onemriganka]

Issue Description:
While reviewing the documentation, I noticed two typos in the README that could confuse contributors and users:

1. The word "Ommitting" should be corrected to "Omitting".

2. The word "exetutables" should be corrected to "executables".

Fixing these typos will improve the clarity and professionalism of the repository's documentation. I propose updating the README accordingly, ensuring consistency and better readability for new contributors.

Summary by CodeRabbit

• Documentation
  • Improved clarity and professionalism by correcting spelling errors in the documentation.

[coderabbitai]

Walkthrough

This pull request updates the documentation by correcting two spelling errors in the README file. The word “Ommitting” is changed to “Omitting” and “exetutables” is changed to “executables”. No modifications have been made to the declarations of exported or public entities.

Changes

File	Change Summary
README.md	Corrected spelling errors: "Ommitting" → "Omitting" and "exetutables" → "executables".

Poem

I’m a rabbit with a joyous cheer,
Hopping over typos that once were here.
A skipped 'm' now found its rightful place,
And corrected words give documentation grace.
With every fix, I wiggle my nose with delight! 🐇✨

---

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 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)

README.md (1)

23-23: Typos Corrected in Documentation

The updated sentence now correctly uses "Omitting" instead of "Ommitting" and "executables" instead of "exetutables," which enhances clarity and professionalism as intended by the PR objectives.

However, note that the sentence still contains some grammatical issues. For example, "while result" appears to be a mistake—consider revising it to "will result" or rephrasing the sentence for clarity. Additionally, you might want to change "any more" to "anymore" to conform with common adverb usage.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~23-~23: Did you mean the adverb “anymore”?
Context: ...ving the option to download executables any more. Create a temporary .env file with y...

(ANY_MORE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 92f8e06 and da3e188.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[uncategorized] ~23-~23: Did you mean the adverb “anymore”?
Context: ...ving the option to download executables any more. Create a temporary .env file with y...

(ANY_MORE)