Start from the current article
Open the article you want to change and inspect the saved brief and body. Confirm the website, audience and intended outcome before asking Iris for an edit.
A precise request is easier to review than “make this better”. For example: “Rewrite the introduction for a first-time buyer, keep the product facts and remove the unsupported performance claim.”
Make a focused change
- Save any manual edits you want to keep.
- Identify the section or wording that needs attention.
- Explain the required outcome and any facts that must remain.
- Use the article’s supported Iris editing or generation action.
- Review the returned change against the original intent.
- Save the result and rerun the relevant QA checks.
Ask for one coherent change at a time when working on sensitive facts, product comparisons or calls to action. This makes it easier to notice an accidental alteration elsewhere.
Check content beyond appearance
Read headings, links, FAQs and key takeaways as well as the main paragraphs. A smooth sentence can still contain an inaccurate product claim or imply a promise the business has not approved.
Word and character counts measure the article body. Styling, editor placeholders and generated publishing blocks are not meaningful extra content. Changing the title or brief should not be treated as adding words to the article itself.
Keep revisions current
Generation and QA use saved versions of the article and brief. If you edit while a background request is running, the result may be rejected as stale. This protects newer work from being overwritten.
After a substantial edit, review images and internal links again. An image or destination that fit the earlier version may no longer match. Previously published content is updated only through the explicit publishing workflow; a private draft edit is not proof of a live change.