What to include in a correction request
For a data or wording correction, include the exact page URL, the sentence or character being questioned, the problem you see and, where possible, a source that supports the correction. A clear example is more useful than a general message saying that a page “feels wrong.” If the issue concerns a simplified or traditional form, include the exact form you want reviewed.
Which request should use which route
Use the custom request page for a tattoo phrase, a Chinese name, a logo character, a blessing or a wording check. Use this contact route for source questions, attribution concerns, broken-link reports, correction requests and general site feedback. Business, legal or payment questions should wait until the relevant contact channel and operating entity are confirmed before launch.
What not to send
Do not send passwords, payment credentials, access keys, government identification numbers or other sensitive records through an ordinary contact message. A project description should contain only the information needed to understand the request. The privacy policy will identify the final retention and deletion process before launch.
Response status
The final mailbox and response process are not configured yet. The current preview should be treated as a planning environment, and a message should not be considered an order, a booking or a promise of response time. Once the channel is live, this page should state the working language, expected response window and escalation path without exposing internal account details.