fix(docs): missing line breaks in why-base page cause text to run together
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open docs/base-chain/quickstart/why-base.mdx and inspect the bullet lists under “A platform for building innovative apps” and “Expansive developer tools.” Compare the source with the rendered why-base page, add the missing separation at both occurrences, and verify that each bullet ends before the following paragraph begins.
Written by the indexing model from the issue text.
Description
Page: https://docs.base.org/base-chain/quickstart/why-base
File: docs/base-chain/quickstart/why-base.mdx
Description
Two bullet points in the body text are missing a line break, causing them to run into the next paragraph.
First occurrence – "A platform for building innovative apps" section:
- Accept payments from anyone, easilyIt's fast, cheap, and permissionless...
Second occurrence – "Expansive developer tools" section:
- Robust developer toolingBut there's more: ...
Expected behavior
Each bullet point should end before the following sentence begins, e.g.:
- Accept payments from anyone, easily
It's fast, cheap, and permissionless...
Steps to reproduce
- Visit https://docs.base.org/base-chain/quickstart/why-base
- Look at the bullet list under "A platform for building innovative apps"
- The last bullet item runs directly into the next paragraph without a line break
Suggested fix
Add a blank line (or move the continuation text outside the list block) after each affected bullet item in the MDX source.
- Dominant language
- JavaScript
- Stars
- 337
- Forks
- 798
- Avg merge
- 7h 24m
- Merged PRs (30d)
- 51
Contributor guide
No contributing guide indexed for this repository
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 base/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·