If you notice any mistakes and don't want to fix them yourself, open an issue on the GitHub page of the book. If you are reading this book with GitBook, you can also create a quick inline comment by clicking the "+" button for the paragraph.
How can I fix a typo? aka quick contributionSelect "Import" and select the folder where you cloned your fork
Clone your fork to your computer
Download and install the Atom editor (or your favorite editors: notepad++, vim, etc.)
Select "Open Folder" and select the folder where you cloned your fork
Edit the book with the help of the Markdown Preview package (Cmd/Ctrl-Shift-M)
Commit and push to your remote repo with your favorite git client (GitHub Desktop, Git BASH, SourceTree, etc.)
Making contributions while you are reading is a good way to learn faster. If you have a hard time understanding something, try to reword it and make a pull request for other readers.
You can also help fixing issues . (Protip for university students: a good GitHub profile is more valuable than a diploma in the job market.)
For every donation on this address, you will appear on http://n.bitcoin.ninja/ .
1KF8kUVHK42XzgcmJF4Lxz4wcL5WDL97PB1KF8kUVHK42XzgcmJF4Lxz4wcL5WDL97PB
The book on GitHub The book on GitBook Code examples on GitHub Hall of the Makers (here are the true makers: those that succeeded in completing the challenges of this book.)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4