Punctuation, phrasing and articles issues

Open Beginner friendly
#215 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
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Open essential-documentation/contribute-to-appflowy/appflowy-mentorship-program/mentorship-2022/mentee-projects/importers.md at the linked section around line 103. Review the listed punctuation, phrasing, and missing-article examples, then make the documented wording corrections. Done means the inaccurate sentences match the provided accurate versions and the surrounding text reads consistently.

Written by the indexing model from the issue text.

Description

https://github.com/AppFlowy-IO/AppFlowy-Docs/blob/25b257ed20e86ededcf0337049fc07d7247d6e34/essential-documentation/contribute-to-appflowy/appflowy-mentorship-program/mentorship-2022/mentee-projects/importers.md?plain=1#L103
Punctuation & Formatting Issues
Inaccurate:
Next step will be importing all the pages present starting from the last level.we are importing...
Accurate:
Next step will be importing all the pages present starting from the last level. We are importing...

Awkward phrasing
Inaccurate:
Next step will be importing all the pages present starting from the last level.
Accurate:
The next step is to import all the pages, starting from the last level.

Missing articles
Inaccurate:
For parent page to show MentionBlock of the subpage it requires the SubPage viewID...
Accurate:
For a parent page to show the MentionBlock of the subpage, it requires the SubPage viewID...

Inaccurate:
which has key as the page name and value as the page viewID
Accurate:
which has the key as the page name and the value as the page viewID.

Dominant language
No language data
Stars
110
Forks
108
PR merge metrics
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.