search

theopensourceway / guidebook

Guidebook of open source community management best practices; is somewhat opinionated.
Other
168 stars 41 forks source link

Typo in contributing documentation (need catch all document for GitHub documentation?) #231

Open aidanmaney opened 1 year ago

aidanmaney commented 1 year ago

I'm not sure this really merits its own issue but I noticed what I believe is a typo in v2.0 In CONTRIBUTING.MD. 

The first bullet in the first numbered subsection under "getting started" reads:

Check the list of outstanding issues to identify something project needs and you'd like to offer.

Should the line say "...to identify something the project needs..." or "...to identify something that the project needs..." ?

Also, I see that there is a catch all document for small fixes and typos for the actual book (the HTML/PDF) but nothing for the GitHub/repo-specific guidelines, credits, etc. If this is a real typo, It would be nice to have an open issue/template to centralize minor alterations to the meta-text.