Editorial Policy

What the guides are for

Every guide exists to solve a practical text-formatting problem: lines broken by a PDF, spaces that will not collapse, characters that cannot be seen, markup that should not be there. A guide earns its place only if someone with that problem would be better off after reading it.

The guides stay within one subject — cleaning and formatting text. The site does not publish general writing advice, marketing content or pages written only to attract search traffic.

How guides are written

• Each guide answers its question at the top, then explains.
• Where a guide describes a cleanup technique, it shows an example of the text before and after. Examples are invented for this site; they are not taken from other websites or from real people’s documents.
• Wording, examples, tables and FAQs are original. Other sites’ text, structure and examples are not copied or closely paraphrased.
• Guides describe what the tools on this site actually do, including where a feature is only a best guess. They do not promise perfect results.
• The site does not publish numbers it cannot support, such as usage figures or made-up statistics.

Use of AI assistance

The guides on this site were drafted with the assistance of AI writing tools, working from written briefs and the site’s content guidelines. This is stated here and at the foot of each guide.

Each guide carries a review status. A guide is described as “reviewed by the publisher” only after the publisher has read it, tried the steps it describes in the live tools, and opened its sources. A guide that has not been through that process says only that it was drafted with AI assistance. All 20 published guides have been reviewed by the publisher.

The site does not describe its content as “expert reviewed” or “fact checked”, and does not attribute guides to named authors, unless that is true of the guide in question.

Technical claims and sources

Technical statements — how a Unicode character behaves, what a file format requires, how a browser feature works — should be checkable. Where a claim needs support, the guide lists its sources at the end. Preference goes to standards and specifications (Unicode, WHATWG, W3C, IETF), then official product documentation, then established technical references.

Sources are summarised in the guide’s own words, not copied. A claim that cannot be supported is softened to what can be observed, or left out. Citations are never invented.

Updates

Guides may be revised when the tools change, when a standard or product changes, or when something can be explained better. Each guide shows the date it was last substantively updated. Dates are not changed for cosmetic edits or to make a page look newer.

Corrections

If you find an error — a wrong statement, a broken example, a step that does not match the tool — please report it through the contact page with the page address and the passage. Confirmed errors are corrected in the guide, and the updated date is changed when the correction affects what the guide says.

Advertising and independence

Guides are not sponsored, and the site does not accept payment for mentions or links. If the site carries advertising, ads are kept separate from the tools and labelled, and advertisers have no say over what the guides recommend.