Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

docs(editorial-style-guide): Fix redundancy, markdown escapes, and add Builder Quick Reference cheat sheet

Open Beginner friendly
#94 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Find the editorial style guide mentioned in the issue and read its introduction, Critical Style Conventions, and Punctuation sections. Check the repeated instruction and escaped asterisks, then compare the proposed quick reference table with the surrounding guide. Done when the duplication and formatting are corrected and the table is added in the requested location.

Written by the indexing model from the issue text.

Description

Summary & Context

In response to @jesse.base.eth's open bounty (Warpcast Cast), this contribution proposes concrete improvements to to enhance editorial clarity, fix formatting discrepancies, and provide an instant cheat sheet for onchain builders.


1. Fix Redundancy in Critical Style Conventions

Under :

  • Current text:
  • Issue: The exact same instruction is duplicated back-to-back within the same bullet point.
  • Proposed Fix:

2. Fix Broken Markdown Escapes in Punctuation

Under :

  • Current text:
  • Issue: Escaped raw asterisks render literal backslashes rather than highlighting the bold comma.
  • Proposed Fix:

3. Proposed Addition: At-A-Glance Builder Quick Reference Table

Builders often need a quick lookup rather than reading the entire guide. Adding this summary table right after the introduction drastically improves document usefulness:

Term / Concept ✅ Use This ❌ Avoid / Do Not Use
Network Name Base BASE, Base Chain, Base Network,
Industry / Movement onchain, Onchain web3, crypto, on-chain, On-Chain
Ecosystem Standing Ethereum L2, onchain economy alt-L1, sidechain, eth killer
Partnership Order
Value Proposition utility, experience, access, community 100x gains, pump, speculative returns, token price
Typography / Case Title Case for headlines Sentence case or ALL-CAPS
Punctuation Oxford comma (A, B, and C) A, B and C (missing Oxford comma)

4. Proposed PR

I have prepared the corresponding patch and am ready to submit a pull request if the core team would like to merge these refinements directly.


💰 Bounty Settlement (Base EVM):
cc @bountybot

Dominant language
No language data
Stars
1.5k
Forks
534
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

  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 base/brand-kit

All issues in base/brand-kit

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.