typo in why-blitz.mdx
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Open why-blitz.mdx and compare the text with the attached image to identify the reported typo. Correct only the typo, then review the rendered page or existing documentation checks to confirm the wording is fixed.
Written by the indexing model from the issue text.
Description
- Dominant language
- MDX
- Stars
- 187
- Forks
- 315
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from blitz-js/blitzjs.com
-
invalid route/link in docs/rpc-setupPossibly taken @justinbalaguer claimed this 722 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 45/100
blitz-js/blitzjs.com#866 ·
-
status/triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
blitz-js/blitzjs.com#850 ·
-
status/triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
blitz-js/blitzjs.com#849 · 1 comment ·
-
status/ready-to-work-on
Difficulty 3/5 1-2 days Newbie friendliness 25/100
blitz-js/blitzjs.com#856 · 2 comments ·
-
status/triage
Difficulty 1/5 Under an hour Newbie friendliness 50/100
blitz-js/blitzjs.com#836 ·
All issues in blitz-js/blitzjs.com
Similar issues
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
labmonkeys-space/nl6#974 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
r-afael/better-yt-recommendations#16 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area:docs documentation good first issue priority:medium
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/microsoft-ui-xaml#12515 · 1 comment · 1 reaction ·
Maintainers usually reply within 2 days