# How to Contribute Documentation Changes Through GitHub

DevFeed: [How to Contribute Documentation Changes Through GitHub](<https://devfeed.tech/articles/tip-edit-the-docs-for-fun-and-profit-19577.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/tip-edit-docs-fun-profit/>)

Author: Shai Almog

Published: 2017-07-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Wiki](<https://devfeed.tech/topics/wiki.md>)

Tags: [docs](<https://devfeed.tech/tags/docs.md>), [github](<https://devfeed.tech/tags/github.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>)

## AI overview

A tutorial explaining how contributors can improve JavaDocs through GitHub and submit the changes as pull requests. It also notes that the Developer Guide can be edited directly in the project wiki.

## Source excerpt

On occasion I answer a question on stackoverflow, the discussion forum or elsewhere and I get a response of the form of: "this wasn't clear from the docs". We improved the docs but befitting a huge project run by engineers without a technical writer in sight this is a bit of a problem... The thing is that this is a problem you can fix regardless of your level in engineering or in English.