fix(docs): inconsistent table header in connecting-to-base
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Open docs/base-chain/quickstart/connecting-to-base.mdx and compare the Base Sepolia manual setup table with the Base Mainnet table. Update the Sepolia header and add the Description row, then verify the rendered page shows the corrected table.
Written by the indexing model from the issue text.
Description
Path: /base-chain/quickstart/connecting-to-base
Page: https://docs.base.org/base-chain/quickstart/connecting-to-base
File: docs/base-chain/quickstart/connecting-to-base.mdx
Description
The MetaMask manual setup table for Base Sepolia has an incorrect and inconsistent first row.
Current (Base Sepolia table):
| Name | Sepolia |
| Network Name | Base Sepolia |
| ... |
The header row says Name | Sepolia which is neither a proper column header nor a data row. The equivalent Base Mainnet table uses Name | Value as the header and includes a Description row with value The public mainnet for Base.
Base Mainnet table for comparison:
| Name | Value |
| Network Name | Base Mainnet |
| Description | The public mainnet for Base. |
| ... |
Suggested fix
Fix the Base Sepolia table header to Name | Value and add a missing Description row:
| Name | Value |
| --- | --- |
| Network Name | Base Sepolia |
| Description | A public testnet for Base. |
| RPC Endpoint | https://sepolia.base.org |
...
- Dominant language
- JavaScript
- Stars
- 337
- Forks
- 798
- Avg merge
- 19h 49m
- Merged PRs (30d)
- 58
Getting set up
We have not checked this project's setup files yet. 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 base/docs
-
Issue on docsOpen
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
Similar issues
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3897 ·
Maintainers usually reply within 2 days
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
check:failed feeds:add
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
iptv-org/database#36179 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day