fix(docs): inconsistent table header in connecting-to-base MetaMask section
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/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 MetaMask table with the Base Mainnet table. Update the Sepolia header and description-row treatment according to one of the stated consistency options, then check the rendered connecting-to-base page to confirm the table is consistent.
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
In the MetaMask manual setup table for Base Sepolia, the first column header reads Name but the first cell value reads Sepolia — which is inconsistent with the equivalent table for Base Mainnet, where the first row is a Description field.
Current (Base Sepolia table):
| Name | Sepolia |
|---|---|
| Network Name | Base Sepolia |
| RPC Endpoint | https://sepolia.base.org |
| ... | ... |
Base Mainnet table for comparison:
| Name | Value |
|---|---|
| Network Name | Base Mainnet |
| Description | The public mainnet for Base. |
| ... | ... |
Expected behavior
The Base Sepolia table should either:
- Add a missing
Descriptionrow (e.g.A public testnet for Base.) to match the Mainnet table, and fix the header toName | Value, or - Remove the inconsistent
Name | Sepoliarow entirely.
Suggested fix
Replace the first row of the Base Sepolia MetaMask table:
| Name | Value |
And add a Description row:
| Description | A public testnet for Base. |
- 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 ·