Corrections

Report a factual issue

We review corrections against primary sources before changing an observation. Preparing this form opens your email application; the site itself does not retain the fields. Include the exact page, disputed statement, current official source, affected scope, and why the source contradicts the published value.

How a correction is reviewed

1. Confirm that the report refers to the same product, plan, model, endpoint, region, runtime, account scope, and version as the published observation.
2. Prefer the platform’s current documentation, help center, changelog, API response headers, or primary technical specification over secondary summaries.
3. Classify the issue as a factual error, a real product change, a documentation clarification, conflicting first-party evidence, or an account-specific value.
4. Update the current observation only when the evidence supports it. Preserve superseded values and add a dated change event when a verifiable before-and-after transition exists.

What happens after acceptance

A material factual correction updates the affected answer, structured observation, source locator, verification date, internal comparisons, tools, and any related error guidance that reused the claim. HyperObserve does not silently rewrite history: genuine older values remain linked as superseded observations when their scope and evidence are known.

Style preferences, unsupported anecdotes, private account behavior, and screenshots without enough scope may be useful leads but are not sufficient by themselves. When official sources conflict, the page should state the conflict rather than choosing the more convenient value.

Read the full editorial methodology, inspect the source register, or browse verified change histories to see how evidence is connected across the site.

Material correction log