Use this checklist before publishing Linux practice notes.
- The note is written in original wording.
- The goal is generalized into a reusable concept or workflow.
- Example paths use neutral placeholders such as
/path/to/project. - File names are generic and not tied to private grading.
- Outputs are self-made, minimal, and only included when they teach command behavior.
- The note does not reproduce private prompt text.
- The note does not include hidden validation requirements.
- The note does not present a final answer set as the main artifact.
- Commands include explanation of why they work.
- Safety-sensitive commands include conservative notes.
- The note links to standard documentation when external authority matters.