practical-tutorials / practical-tutorials/project-based-learning
Revise an explanation
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 284k
- Forks
- 36.3k
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
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.
Research direction
Open the linked tree-sitter-solidity commit first and inspect the explanation it changes. Then search this repository for the corresponding text and compare it with the commit. Done means the relevant explanation has been revised to match the intended wording or content from the linked commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100