Skip to main content
Use document correction when the generated artifact is readable but contains an inaccurate, incomplete, or poorly framed section. Correct upstream profile or competitor context first when the same error affects several documents.

Prepare the correction

Before submitting a brief:
  • identify the exact document and section;
  • separate factual errors from style preferences;
  • provide the correct fact or approved wording;
  • state what should remain unchanged;
  • check whether an active competitor change is already updating the document.

Submit a correction

1

Open the document

Select a ready document from the Company panel.
2

Read the full context

Confirm that the problem is in this document and not an upstream company-profile or competitor error.
3

Select the correction control

Use the edit control beside the title. A lock opens the plan explanation instead of a text field.
4

Write a bounded brief

Name the section, correction, evidence, and constraints. Submit one coherent intent.
5

Follow Rewriting

The current body remains readable while Rewriting… is shown. Do not submit a second correction against the same document.
6

Verify the new version

Re-read the changed section and scan nearby sections for accidental contradictions.

Example brief

In the Target audience section, replace “enterprise security teams” with “security teams at companies with 50 to 500 employees.” Keep the existing healthcare and fintech examples. Do not change the positioning statement or channel priorities.

Rewriting versus updating

  • Rewriting… means someone requested a direct document correction.
  • Updating… means Alesta is reconciling the document after an upstream change, such as a competitor-set update.
Wait for an active update to finish before deciding whether a direct correction is still necessary.

Copy and share safely

Use the copy control to copy the current body. Links inside the reader open in a new tab. Before sharing:
  • confirm the document is no longer rewriting or updating;
  • remove unsupported internal assumptions;
  • preserve caveats around unavailable evidence;
  • verify competitor and pricing claims against their source;
  • obtain any required legal or brand approval.

If the action fails

Read the displayed reason. Common boundaries include plan access, exhausted credits, another action running on the same document, or a model output that could not be completed. The existing document remains readable unless the server says otherwise.

References