Tense, Article, and Sentence Structure Errors

Open Beginner friendly
#245 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Open essential-documentation/contribute-to-appflowy/write-for-appflowy/drafts/draft-how-to-add-a-new-property-to-appflowy-database.md and inspect the linked passage around line 85. Apply the listed tense, article, punctuation, and sentence-structure corrections, then review the surrounding text to ensure the wording is consistent and grammatically clear.

Written by the indexing model from the issue text.

Description

https://github.com/AppFlowy-IO/AppFlowy-Docs/blob/cb1d8a02d240749c85bb75e37c96b9903393f235/essential-documentation/contribute-to-appflowy/write-for-appflowy/drafts/draft-how-to-add-a-new-property-to-appflowy-database.md?plain=1#L85

Identified Errors with Corrections:

  1. Awkward phrasing / tense mismatch:

    • Inaccurate:
      "on adding CreatedAt and UpdatedAt property type has got merged."
    • Accurate:
      "about adding the CreatedAt and UpdatedAt property types, which has just been merged."
      (Also pluralize “type” to “types”)

  2. Missing punctuation / clarity:

    • Inaccurate:
      "So when you are reading this Appflowy has these two types as a property type."
    • Accurate:
      "So when you are reading this, AppFlowy already has these two types as property types."

  3. Unclear subject in compound sentence:

    • Inaccurate:
      "I won't go through detail every specifics..."
    • Accurate:
      "I won’t go into detail on every specific..."
      (Correct “go through” → “go into”; “detail” is uncountable; “specifics” → “specific” for clarity.)

  4. Article Usage & Style:

    • Inaccurate:
      "but I will elaborate the parts which I think are essential."
    • Accurate:
      "but I will elaborate on the parts that I think are essential."
Dominant language
No language data
Stars
110
Forks
108
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AppFlowy-IO/AppFlowy-Docs

All issues in AppFlowy-IO/AppFlowy-Docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.