From e7ad7eb90b02e9a576e6281cce46494d8b62996c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Wed, 27 May 2020 22:31:18 +0200 Subject: [PATCH] doc: Reword unclear sentence about programs. Fixes . Reported by Jan Synacek . * doc/ref/api-procedures.texi (Compiled Procedures): Clarify wording. --- doc/ref/api-procedures.texi | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/ref/api-procedures.texi b/doc/ref/api-procedures.texi index df24178f9..461112c8a 100644 --- a/doc/ref/api-procedures.texi +++ b/doc/ref/api-procedures.texi @@ -143,9 +143,11 @@ loaded, and save the result to disk. Procedures can be compiled at runtime as well. @xref{Read/Load/Eval/Compile}, for more information on runtime compilation. -Compiled procedures, also known as @dfn{programs}, respond all -procedures that operate on procedures. In addition, there are a few -more accessors for low-level details on programs. +Compiled procedures, also known as @dfn{programs}, respond to all +procedures that operate on procedures: you can pass a program to +@code{procedure?}, @code{procedure-name}, and so on (@pxref{Procedure +Properties}). In addition, there are a few more accessors for low-level +details on programs. Most people won't need to use the routines described in this section, but it's good to have them documented. You'll have to include the