Clear, specific feedback helps eWiki keep practical AI guidance accurate and useful. Use this page to report a step that no longer works, describe a problem our guidance did not solve, request a correction, or suggest a task you would like us to cover. You can submit feedback without creating an account.
Choose the feedback type that fits
Selecting the closest feedback type helps route your message for review:
– Changed step: A product interface, setting, workflow, file requirement, or access path differs from what a guide describes. – Unresolved problem: You followed the available guidance but still encountered an error, poor result, or unclear decision point. – Correction request: A statement, definition, caption, comparison field, or cited detail appears inaccurate or misleading. – Topic suggestion: You need help with an AI image, video, or general workflow that eWiki does not yet explain. – General feedback: Your message concerns accessibility, navigation, clarity, or another aspect of the site.
If more than one type applies, choose the main reason for contacting us and explain the related issue in your message.
Report a changed or broken step
A useful changed-step report identifies the page, the step involved, and what you observed instead. Include the tool or service name, the device or platform, and any relevant file format when those details affect the workflow. If the change concerns a product interface, describe the control or option in plain language rather than assuming reviewers can see the same version.
Screenshots can provide context, but remove account names, email addresses, order details, private media, API keys, and other sensitive information before attaching or sharing anything. A report does not need to include proprietary files for us to understand the problem.
Explain an unresolved problem
Tell us what you were trying to produce, which steps you completed, and where the result stopped matching your goal. For image tasks, useful details may include unwanted edges, transparency problems, incorrect colors, missing objects, or export issues. For video tasks, mention symptoms such as unstable motion, cropping, background artifacts, timing problems, or an unsupported input.
Error wording can be helpful when it does not contain private data. Also note whether the issue happens consistently or only with a particular file or setting. These details make it easier to distinguish a documentation gap from a tool limitation or a problem that requires additional verification.
Request a factual correction
Correction requests should identify the exact claim or section and explain why it may be wrong. When possible, include a reliable source, an official product notice, or a reproducible observation. We assess corrections against the available evidence and may revise, clarify, qualify, or remove a statement when warranted.
Disagreement alone does not automatically establish an error, but well-supported challenges are welcome. Claims involving current pricing, product availability, interface behavior, and feature limits can change quickly and may require fresh verification before an update is published.
Suggest a new task or guide
Describe the outcome you want, not only the name of a tool. For example, explain the type of image or video you are working with, the desired result, your experience level, and any constraints such as preserving transparency or preparing product media. This helps us understand the underlying need without assuming that one product is the right solution.
Suggestions inform editorial planning, but submitting an idea does not guarantee publication, testing, or a recommendation. We prioritize topics according to reader usefulness, available evidence, and whether the task can be explained responsibly.
Protect your privacy
Share only the information needed to understand your message. Do not submit passwords, authentication codes, API credentials, payment information, confidential business material, or personal data belonging to someone else. If sample media is essential, use a version you are authorized to share and remove identifying details wherever practical.
Information submitted through this page should be used to evaluate the request, investigate potential issues, and improve relevant guidance. Applicable handling details and visitor choices are described in the site’s privacy information.
What to expect after submitting
Every clear report can contribute to editorial review, but a personal reply is not guaranteed. Complex corrections and changing product behavior may take longer to assess because evidence must be checked before guidance is updated. Duplicate messages may be grouped, and requests that lack enough detail may remain unresolved until the issue can be reproduced or independently confirmed.
For the most useful submission, name the affected page or task, describe what happened, state what you expected, and include non-sensitive evidence when available.
Improve this guide
Report a problem or suggest the next question
Submissions enter a private editorial queue. They are reviewed and deduplicated before any public update or new page is created.