Skip to content

docs: improve README wording and fix grammar issues#3341

Open
Dorra21 wants to merge 1 commit into
RocketChat:masterfrom
Dorra21:docs-readme-fixes
Open

docs: improve README wording and fix grammar issues#3341
Dorra21 wants to merge 1 commit into
RocketChat:masterfrom
Dorra21:docs-readme-fixes

Conversation

@Dorra21
Copy link
Copy Markdown

@Dorra21 Dorra21 commented May 25, 2026

This PR improves README documentation by fixing minor grammar issues and improving wording clarity.

No functional changes were made.

Summary by CodeRabbit

  • Documentation
    • Improved README formatting and refined wording across multiple sections, including installation instructions, development setup, and engagement information for enhanced clarity and readability.

Review Change Stack

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
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
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 25, 2026

Walkthrough

README.md receives multiple minor wording refinements and formatting improvements across six sections: the introduction is reformatted with a trailing comma and line breaks, the subscription description is rewritten, Windows installation instructions are rephrased, build documentation changes word choice, the build pipeline intro is reworded, and the release instructions are reformatted into a code block. No behavioral changes or documented functionality is altered.

Changes

README Documentation Improvements

Layer / File(s) Summary
Documentation wording and formatting updates
README.md
Introduction sentence adds a trailing comma and splits Electron-based build wording across lines. "Subscribe for Updates" section removes inline sign-up callout. Windows installation paragraph is rephrased. Build description changes "all stuff" to "all files." Build pipeline intro changes "founded upon" to "based on." Release section reformats yarn release into a fenced code block and adjusts surrounding grammar.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

type: chore

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: documentation improvements to the README with grammar and wording fixes, which matches the changeset content.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
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: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 152: Replace the sentence "It will start the packaging process for the
operating system on which you are running this command. Ready for distribution
file will be outputted to `dist` directory." with a grammatically corrected
version: "It will start the packaging process for the operating system on which
you are running this command. The ready-for-distribution file will be output to
the `dist` directory." — update the README line that contains "Ready for
distribution file" and "outputted" to use the hyphenated compound adjective,
"output" as the past participle, and include the article "the" before "dist
directory".
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2a1415be-f121-4ea3-a60f-50471e1a9981

📥 Commits

Reviewing files that changed from the base of the PR and between c2b584b and 2b03058.

📒 Files selected for processing (1)
  • README.md
📜 Review details
🧰 Additional context used
🪛 LanguageTool
README.md

[grammar] ~152-~152: Use a hyphen to join words.
Context: ... you are running this command. Ready for distribution file will be outputted to `...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (6)
README.md (6)

8-9: LGTM!


34-35: LGTM!


53-53: LGTM!


85-85: LGTM!


96-96: LGTM!


146-150: LGTM!

Comment thread README.md

It will start the packaging process for operating system you are running this
command on. Ready for distribution file will be outputted to `dist` directory.
It will start the packaging process for the operating system on which you are running this command. Ready for distribution file will be outputted to `dist` directory.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix grammar and word choice issues.

This sentence has several issues:

  • "Ready for distribution file" should be hyphenated as a compound adjective: "ready-for-distribution file"
  • "outputted" should be "output" (standard past participle)
  • Missing article "the" before "dist directory"
✏️ Proposed fix
-It will start the packaging process for the operating system on which you are running this command. Ready for distribution file will be outputted to `dist` directory.
+It will start the packaging process for the operating system you are running this command on. The ready-for-distribution file will be output to the `dist` directory.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
It will start the packaging process for the operating system on which you are running this command. Ready for distribution file will be outputted to `dist` directory.
It will start the packaging process for the operating system you are running this command on. The ready-for-distribution file will be output to the `dist` directory.
🧰 Tools
🪛 LanguageTool

[grammar] ~152-~152: Use a hyphen to join words.
Context: ... you are running this command. Ready for distribution file will be outputted to `...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 152, Replace the sentence "It will start the packaging
process for the operating system on which you are running this command. Ready
for distribution file will be outputted to `dist` directory." with a
grammatically corrected version: "It will start the packaging process for the
operating system on which you are running this command. The
ready-for-distribution file will be output to the `dist` directory." — update
the README line that contains "Ready for distribution file" and "outputted" to
use the hyphenated compound adjective, "output" as the past participle, and
include the article "the" before "dist directory".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants