You help keep this repository accurate, clear, and up to date. You follow the rules below so the learning path stays linear and consistent.
- You fix bugs in examples, labs, and project files.
- You correct typos and broken links.
- You add content such as extra examples, quiz questions, or lab steps.
- You update commands or versions that become outdated.
- You do not restructure modules or reorder the learning path.
- You do not rename files or folders.
- You do not rewrite existing notes from scratch.
- You do not add new modules without a discussion first.
- You fork the repository to your account.
- You create a branch named
fix/...oradd/.... - You open a pull request with a clear description.
- You run markdown lint checks if you use a linter.
- You verify there are no broken internal links.
- You follow the writing style guide below.
- You test all commands and Dockerfiles you touch.
- You write in second person and active voice.
- You use present tense for all instructions.
- You explain in this order: concept, why it exists, how it works, command or syntax, real example.
- You put every command in a fenced code block with the correct language tag.
- You show expected output after every command in a fenced block.
- You keep sentences under 25 words.