Skip to content

docs(EL): fix JSON-RPC hex example (use 0x0400 as invalid case)#486

Open
adi611 wants to merge 1 commit intoeth-protocol-fellows:mainfrom
adi611:fix/json-rpc-hex-example
Open

docs(EL): fix JSON-RPC hex example (use 0x0400 as invalid case)#486
adi611 wants to merge 1 commit intoeth-protocol-fellows:mainfrom
adi611:fix/json-rpc-hex-example

Conversation

@adi611
Copy link

@adi611 adi611 commented Feb 23, 2026

Wiki PR Checklist

Thank you for contributing to the Protocol Wiki! Before you open a PR, make sure to read information for contributors and take a look at following checklist:

  • Describe your changes, substitute this text with the information
  • If you are touching an existing piece of content, ask the relevant maintainer for review
  • If you need feedback for your content from wider community, share the PR in our Discord
  • Review changes to ensure there are no typos, see instructions bellow

@github-actions
Copy link

Hi @adi611,

⚠️ Potential typos found in your pull request:

  • 📄 ./docs/eps/intro.md (line(s) 21):
    1. ❌ excercises
  • 📄 ./docs/eps/intro.md (line(s) 21):
    1. ❌ quizes
  • 📄 ./docs/wiki/EL/el-specs.md (line(s) 1093):
    1. ❌ Finalisation
  • 📄 ./docs/wiki/EL/el-data-structures-summary.md (line(s) 8,21):
    1. ❌ prev
  • 📄 ./docs/wiki/EL/el-architecture.md (line(s) 305):
    1. ❌ backends
  • 📄 ./docs/wiki/EL/el-architecture.md (line(s) 313,322):
    1. ❌ memtable
  • 📄 ./docs/wiki/EL/el-architecture.md (line(s) 313,322):
    1. ❌ memtable
  • 📄 ./docs/wiki/EL/el-architecture.md (line(s) 315):
    1. ❌ reimplementations
  • 📄 ./docs/readme.md (line(s) 7,23):
    1. ❌ annualy
  • 📄 ./docs/readme.md (line(s) 7,23):
    1. ❌ annualy

ℹ️ How to fix this error:

  1. If these are actual typos:

    • Open the files at the specified line numbers and fix them
  2. If these are names or one-off nouns:

    • Wrap them in <name> tags
    • Example: <name>Alex Pereira</name>
    • Use this for people's names or unique terms that appear rarely
  3. If these are valid terms:

    • Add them to wordlist.txt (one word per line)
    • Terms must be plain text without spaces/special chars
    • The list is case-insensitive
  4. If these are code terms:

    • Wrap them in backticks (`) in your markdown

ℹ️ Checking for typos locally

  1. Install aspell for your platform
  2. Navigate to project root and run:
for f in **/*.md ; do echo $f ; aspell --lang=en_US --mode=markdown --home-dir=. --personal=wordlist.txt --ignore-case=true --camel-case --add-sgml-skip nospellcheck list < $f | sort | uniq -c ; done

Learn more about wordlist format

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant