Trust

Corrections and Publication Updates

The short answer

Send corrections to [email protected] with the affected URL, statement, exact model or revision, and a useful source. A changed price, a wrong specification and an unresolved document conflict need different responses; identify which issue you found.

Better information, clearly corrected. Page · claim · supporting source
A specific report makes a correction easier to investigate.

Report a specific issue

Email [email protected] with the page address, section, exact board or revision, and the wording that needs attention. Add the manual, selected product configuration or official support statement that helps resolve the issue. A screenshot can identify a changing listing but may not identify the unit being sold.

Keep the message focused on the editorial claim. A seller handles orders, payments and warranty cases, so this route does not need your payment details. The contact page gives the alternative telephone contact.

How a claim is reassessed

Check the selected configuration and source against the published statement. Distinguish an inaccurate fact from a changed price, unavailable order or disagreement between two official documents. If the current revision cannot be established, keep that limitation explicit rather than choose a convenient figure.

An affected recommendation or tool entry may need changing if the issue alters buyer suitability, price eligibility or an operating limit. Private records retain the actual check and reasoning. Material corrections can be explained with the affected coverage.

What this page does not imply

Unresolved specification discrepancies are explained in the relevant guides. When a manufacturer or seller clarifies an issue, the affected recommendation and source record should reflect that answer. A reported discrepancy does not establish that a particular unit is affected.

The editorial policy covers source standards and the source record provides the official material used in published articles.

Sources and method for this article

Keep exploring

Where to go next