- Read the gbdev wide contribution guidelines
- Run an English spell checker
- Try to split the PR in small, self-contained parts so they can be reviewed and merged faster (and independently)
- Make sure the code you are adding/changing follows the GB ASM Style guide
- When adding new content, give first a read to the existing chapters to get an idea of the style and teaching strategies of the document
- gb-asm-tutorial is powered by the same preprocessors and renderers we developed for Pan Docs. This gives you additional features over plain Markdown, most notably the "custom containers". To see how to use them, read the "Special markup" paragraph of the Pan Docs' CONTRIBUTING.md