In this guide
Define the task boundaryCheck source and applicabilityUse honest examplesClose the update clearlyA useful help article answers a specific question and states the supported next step. It should not turn an agent’s recollection into a product promise. Review the public copy against current primary documentation and the exact service facts before reusing it in customer cases.
Define the task boundary
State what the article helps the reader do. A guide to finding a player receipt is different from a service renewal instruction. Keep nearby topics linked rather than repeating a broad generic checklist. Remove claims that the article’s sources do not establish.
Check source and applicability
Use the responsible developer, manufacturer or provider for rules and technical steps. Record the checked date and relevant version or account scope. A forum workaround can suggest a question, but it should not establish an official compatibility or security claim.
| Review field | Question |
|---|---|
| Intent | Does this answer one distinct need? |
| Evidence | Does the primary source support the claim? |
| Scope | Which app, version or account does it apply to? |
| Maintenance | What change would require a review? |
Use honest examples
Label fictional accounts, calculations and timelines. Never insert live credentials or customer screenshots into public training copy. Do not claim personal testing when the work was documentation research. A source link to a feature does not prove that every device or external service was tested with it.
Close the update clearly
Record what changed and why in the internal editorial note. Retire outdated instructions or mark them superseded where appropriate. Keep customer-facing text focused on the task rather than internal production labels. This procedure describes a review method, not a certification or a claim about Dream’s internal editorial staff.
Questions about this guide
Can I keep an old instruction because customers recognise its screenshot?
Only if it still accurately represents the supported process. Familiarity does not make an obsolete instruction correct. Update the steps and provide useful text context so customers can follow the current interface even when the picture changes.