> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcdemo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Keep a demo current

> Review product changes, update the draft, and replace what viewers see deliberately.

A captured demo is a representation of a product at a point in time. A renamed button, changed screen, or outdated example can make a good story misleading. Give each important demo an owner and a review cadence that matches how often its product changes.

## When a product changes

1. Find where the demo is used: shared links, embedded pages, sales material, and support articles. Decide whether the change affects a critical instruction or only a visual detail.
2. Open the draft and walk the affected path. Compare the capture, guide text, link targets, and ending against the current product.
3. Make the smallest reliable update. For an HTML step, the editor can adjust selected page content; a screenshot or video may need an image edit or a fresh capture. For a sandbox, check the connected states and links as well as the changed screen. See [Recapture a changed screen](https://docs.arcdemo.io/guides/recapture.md) for the HTML workflow and review options.
4. Test the complete path, not only the edited step. A changed label or destination can make the preceding instruction or a branch confusing.
5. Publish the reviewed draft, then check the actual shared link and embed. Until publishing, viewers keep seeing the earlier published version.

## Make a safe revision

Use [History](https://docs.arcdemo.io/editor/version-history.md) to inspect available revisions before restoring. Restoring replaces the current draft, so read the review of affected content and make sure the selected revision is the one you intend. A restore is not live until it is published.

If you need a separate audience-specific version, [duplicate the demo](https://docs.arcdemo.io/workspace/organize.md). A duplicate is a new private draft; analytics, leads, share links, and revision history do not carry over. Review and publish it separately.

If the demo should no longer be available, identify the links and embeds that depend on it before taking it offline. Replace or remove those references so readers are not sent to a dead end.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.