PHW99Go · Reader information

How We Check a Reading Guide

A clear explanation should show where the fact ends and the example begins. This is the method used for the first PHW99Go collection.

Use an identifiable source

We prefer a named provider’s public document for product-specific statements, a regulator’s own publication for a regulatory reference and a standards body’s material for accessibility concepts. A foreign rule is labelled with its own jurisdiction. An overview is not silently promoted into a full rules manual.

Separate facts, observations and examples

An article states whether a diagram is original and whether a numerical sequence is invented. A screenshot supports only the visible details and known context. We do not manufacture experience of installing an app, playing a game, testing a server or inspecting an account.

Keep dates honest

Publication and modification dates describe this article’s actual history. A source reading date is the date it was checked, not the date its underlying product changed. We do not refresh dates solely because a monitoring task ran.

Correct the smallest supported claim

When a source changes or a reader identifies an error, compare the specific sentence with the named document. Amend the affected text, explain any meaningful correction and update its modification date. Keep unsupported configuration claims out of the article instead of filling gaps with guesses.

Prepare a correction

Use the correction-note page to organise a source URL and the sentence in question. The note is prepared locally and does not send a message to us.