Human review & edit of User guide

[lastobelus]

Outcome

A human editorial pass makes the deployed user guide clearer, more concise, and easier to trust before the broad public announcement, without mixing contributor implementation detail back into user documentation.

Timing

Do this late in the Broad announcement gate, after focused-preview feedback and the final issue #9 durability claims have stabilized.

Acceptance criteria

• A human reviews the complete user-guide path as a prospective Markover user.
• Awkward wording, repetition, tone, grammar, and navigation issues are edited directly.
• User and developer documentation remain clearly segregated; user pages contain only choices, actions, risks, limitations, and recovery guidance relevant to users.
• Commands, requirements, links, screenshots, and cross-page claims are checked against the then-current product.
• Desktop and narrow layouts receive a final visual review.
• Documentation tests are updated only where they protect useful semantic contracts rather than exact prose.

Scope boundaries

This issue is an editorial and usability review. It does not add product behavior, broaden compatibility promises, invent durability guarantees, or move contributor mechanics into the user guide.