Help us make the next version better.

A useful bug report

Start with the smallest example that shows the problem. Use invented text instead of a private dream. You can copy this outline:

• Page or feature:
• What I tried, in order:
• What I expected:
• What actually happened, including any visible error:
• Device and browser, if known:
• Does it happen every time or only sometimes?

A meaning, fact or source needs correction

Send the page URL and the exact statement that concerns you. Explain whether the issue is a factual error, a citation that does not support the claim, a cultural perspective that needs context or an interpretation that does not fit. A source title, link and relevant passage can help us examine it.

For a personal reading, its fit and correction controls keep feedback connected to that reading. A private support request is separate from the optional structured interpretation-improvement contribution pool.

An accessibility barrier

Tell us what you could not reach, read, hear or operate, and the page where it happened. If useful, include your browser, device, zoom setting or assistive technology. You do not need to disclose a diagnosis. Describe the format or change that would help.

A feature wish or a better resource

Describe the task you want to finish, your current workaround and why it matters. For a resource suggestion, include a link, the intended reader, access costs and any relationship you have with its provider.

Founding testers can suggest and vote on wishes in Tester Studio. A wish is shared with other testers only when you choose that audience. Submission does not guarantee adoption or a release date.

What happens next

Requests submitted through Support have a status and response on the website. Email conversations continue in your inbox. We may ask for a smaller example or more context. Avoid sending the same private material through several channels.

Confirmed public-content errors should lead to a correction or removal of the affected statement, with a dated change note for a substantive revision. Suggestions remain proposals until a change is actually published. We do not promise a fixed response time.

Keep the report safe

Do not include passwords, recovery codes, payment-card details, complete private dream accounts or another person's information. For a security concern or harmful interaction, use the private routes on Safety instead of a public wish or community post.