Draft User Manual

Style rules

• Prefer direct instructional language.
• Explain why a step matters only when it prevents mistakes or reduces operator confusion.
• Keep examples concrete: real filenames, service names, ports, commands, and directories when available.
• For translated manuals, keep technical terminology stable and natural in the target language instead of translating identifiers mechanically.
• When updating an existing manual, preserve confirmed structure where possible and improve clarity with minimal churn.

Output shape

• Start with a title that matches the actual deliverable.
• Add a short introduction that states the manual's audience and scope.
• Use numbered steps for procedures and flat bullets for inventories or checks.
• Separate prerequisites from execution steps.
• End with operational checks, troubleshooting notes, or known limitations when the source supports them.

References

• Read references/example-en.md when a concrete English example helps with structure, tone, or section ordering.
• If the current repository already contains a user manual draft, treat that file as the primary style and fact source for revisions.