@@ -65,7 +65,7 @@ export const Elicitation: Api<ElicitationApi> = createApi<ElicitationApi>("Elici
       "no elicitation provider configured — a host installs one with " +
         'yield* Elicitation.around({ *elicit([request], next) { ... } }, { at: "min" }). ' +
         "`xmd run` installs the WebForm provider; under `xmd test`, supply the answer " +
-        "with an <Answers> region or scriptElicitations().",
+        "with an <Answers> region.",
     );
   },
 });
@@ -806,8 +806,8 @@ export default define.page(function Components() {
         schema defines every response available. Where the question is actually
         put to someone is the host's decision, installed through the Elicitation
         Api — a browser form under the CLI today, a terminal or an editor
-        integration later, scripted answers under a test. Swapping one for
-        another changes no Markdown.
+        integration later, or answers the document supplies itself. Swapping one
+        for another changes no Markdown.
       </p>
       <p>
         That is the reason it is contextual rather than an author-facing option.
 
@@ -5044,8 +5044,7 @@ shape of provider, and replacing one with another changes no executable Markdown
 `xmd test` deliberately installs no provider. A test document that elicits
 without saying what the answer is would otherwise open a browser and wait for
 somebody who is not coming; with none installed it fails immediately, and an
-`<Answers>` region (§6.16.2) or scripted middleware is how a test says what the
-answer is.
+`<Answers>` region (§6.16.2) is how a test says what the answer is.
 
 The elicitation path is also callable by a host directly — `elicit({ message,
 schema })`, or the `prepareElicitation`/`runPreparedElicitation` split when the