> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/exercise-editor/search-and-replace.md).
# Search & Replace
Search & Replace allows the designer to **search and replace content** across the Editor from one central place.
| Benefit | Feature |
| ----------------------------- | ---------------------------------------------------- |
| Save significant editing time | Replace words and phrases selectively or all at once |
| Reduce manual effort | Expand results for clarity before replacing |
### Where can I find search & replace?
Search & replace is available from:
1. **Master Events List** (MEL)
2. **Persona library** (historical content only - you can't search and replace names/bios etc.)
3. **Pattern of Life** (PoL)
Search & replace can be accessed via an icon of a **magnifying glass**, found at the bottom-right of the screen:
Search for specific words and type below what you want to replace them with. You can select individual injects, or *Select all results* to replace all usages:
Icon
Use
▼
Keeps last search
✕
Closes panel and resets search
{% hint style="danger" %}
Leaving the fields empty or typing only a space will delete the word.
{% endhint %}
### :zap:Smartwords
* The platform treats all words as static, so **Smartwords are replaced like normal text**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/exercise-editor/search-and-replace.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
