Skip to content

docs: fix typos and grammar in QF documentation#2320

Open
HusseinAdeiza wants to merge 1 commit into
Giveth:stagingfrom
HusseinAdeiza:docs/fix-typos-and-grammar
Open

docs: fix typos and grammar in QF documentation#2320
HusseinAdeiza wants to merge 1 commit into
Giveth:stagingfrom
HusseinAdeiza:docs/fix-typos-and-grammar

Conversation

@HusseinAdeiza
Copy link
Copy Markdown

@HusseinAdeiza HusseinAdeiza commented May 8, 2026

Summary

This PR fixes several typos and grammar issues in the Quadratic Funding (QF) documentation to improve clarity and consistency.

Changes Made

docs/qfRoundMatchingFundCalculation.md

  • Fixed "detail" to "details" (line 4)
  • Added missing apostrophe in "don't" (line 34)

docs/qfRoundInstruction.md

  • Fixed "be active" to "to be active" (line 6)
  • Changed "just" to "only" for better clarity (line 6)
  • Added missing articles "the" and "is" (line 10)
  • Fixed "can not" to "cannot" (line 10)
  • Capitalized "QF" and made "detail" plural (line 21)
  • Fixed "project" to "projects" (line 28)

Impact

  • Improves documentation readability
  • Ensures grammatical consistency
  • Makes instructions clearer for users

Type of Change

  • Documentation update
  • Grammar/typo fixes

Summary by CodeRabbit

  • Documentation
    • Refined QF Round admin UI documentation with clearer wording and improved guidance for round creation, status management, and project operations
    • Enhanced explanations for QF Round details viewing and project selection workflows
    • Corrected grammar and punctuation in matching fund calculation documentation

- Fix 'detail' to 'details' in qfRoundMatchingFundCalculation.md
- Add missing apostrophe in 'don't'
- Fix 'be active' to 'to be active'
- Change 'just' to 'only' for clarity
- Add missing articles 'the' and 'is'
- Fix 'can not' to 'cannot'
- Change 'qf round detail' to 'QF round details'
- Fix 'multiple project' to 'multiple projects'

Improves documentation clarity and grammar consistency.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

Review Change Stack

Walkthrough

This PR refines documentation across two QF Round files. The admin UI instructions clarify field descriptions and workflow steps for creating, viewing, and managing projects in QF rounds. The matching fund calculation documentation corrects minor grammar and punctuation errors. All changes are text-only with no code modifications.

Changes

QF Round Documentation Refinement

Layer / File(s) Summary
Admin UI Instructions
docs/qfRoundInstruction.md
Create section refines Is Active, Begin Date, and End Date descriptions; Show Single QF Round section adds detail view description; Add Projects section corrects grammar and clarifies multi-project selection with button usage.
Matching Fund Documentation
docs/qfRoundMatchingFundCalculation.md
Formula section corrects "detail" to "details"; Estimated Matching section corrects "dont" to "don't".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through docs with care,
Polishing words with gentle flair,
"Don't" and "details" now shine so bright,
Admin guidance, clear and right,
Gitcoin's wisdom, spelled just right! 🐰✨

🚥 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 and accurately summarizes the main change: fixing typos and grammar in QF documentation, which aligns with all modifications across both files.
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.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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

🧹 Nitpick comments (1)
docs/qfRoundInstruction.md (1)

9-10: 💤 Low value

Optional: Consider varying the phrasing.

Both the Begin Date and End Date descriptions start with "Exact time of when", which creates repetition. Consider varying one of them for better readability.

✍️ Example variation
 * **Begin Date** Exact time of when we want to begin round
-* **End Date** Exact time of when the round is supposed to end **be careful of this field, because when the end date passes, admins cannot edit the round anymore**
+* **End Date** The precise moment when the round is supposed to end **be careful of this field, because when the end date passes, admins cannot edit the round anymore**
🤖 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 `@docs/qfRoundInstruction.md` around lines 9 - 10, The two field descriptions
("Begin Date" and "End Date") repeat "Exact time of when"; update one (or both)
to vary phrasing for readability—e.g., change "Begin Date" to "The exact
timestamp to start the round" and change "End Date" to "The timestamp when the
round ends; when it passes admins cannot edit the round anymore" (or any
equivalent wording that preserves the warning about editability). Ensure you
modify the strings associated with the "Begin Date" and "End Date" entries in
the doc so the repetition is removed while keeping the existing caution about
the End Date.
🤖 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 `@docs/qfRoundInstruction.md`:
- Line 21: The sentence "You can see QF round details and related projects of a
qf round in this page" has inconsistent capitalization and a preposition issue;
update it to use a single consistent form (e.g., "QF round" everywhere) and
change "in this page" to "on this page" so it reads: "You can see QF round
details and related projects of a QF round on this page" (or choose the
alternate preferred casing and apply it to both occurrences of "QF round"/"qf
round").

---

Nitpick comments:
In `@docs/qfRoundInstruction.md`:
- Around line 9-10: The two field descriptions ("Begin Date" and "End Date")
repeat "Exact time of when"; update one (or both) to vary phrasing for
readability—e.g., change "Begin Date" to "The exact timestamp to start the
round" and change "End Date" to "The timestamp when the round ends; when it
passes admins cannot edit the round anymore" (or any equivalent wording that
preserves the warning about editability). Ensure you modify the strings
associated with the "Begin Date" and "End Date" entries in the doc so the
repetition is removed while keeping the existing caution about the End Date.
🪄 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: 530c9910-1253-408d-ad44-7fd750d1c6ca

📥 Commits

Reviewing files that changed from the base of the PR and between 424ffe7 and a1d6ba0.

📒 Files selected for processing (2)
  • docs/qfRoundInstruction.md
  • docs/qfRoundMatchingFundCalculation.md

<img width="1733" alt="Screen Shot 1402-04-20 at 12 10 16" src="https://github.com/Giveth/impact-graph/assets/9850545/239f9fe9-4684-4789-b2c6-11ad62f0a6a2">

You can see qf round detail and related projects of a qf round in this page
You can see QF round details and related projects of a qf round in this page
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 capitalization inconsistency within the same sentence.

The sentence uses both "QF round" and "qf round" inconsistently. Choose one capitalization style and apply it throughout.

📝 Proposed fix for consistency
-You can see QF round details and related projects of a qf round in this page
+You can see QF round details and related projects in this page

Or, if you want to be more explicit:

-You can see QF round details and related projects of a qf round in this page
+You can see QF Round details and related projects of a QF Round in this page

Additionally, consider "on this page" instead of "in this page" for better English.

📝 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
You can see QF round details and related projects of a qf round in this page
You can see QF round details and related projects in this page
Suggested change
You can see QF round details and related projects of a qf round in this page
You can see QF Round details and related projects of a QF Round in this page
🤖 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 `@docs/qfRoundInstruction.md` at line 21, The sentence "You can see QF round
details and related projects of a qf round in this page" has inconsistent
capitalization and a preposition issue; update it to use a single consistent
form (e.g., "QF round" everywhere) and change "in this page" to "on this page"
so it reads: "You can see QF round details and related projects of a QF round on
this page" (or choose the alternate preferred casing and apply it to both
occurrences of "QF round"/"qf round").

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