diff options
| -rw-r--r-- | doc/lispref/objects.texi | 2 | ||||
| -rw-r--r-- | doc/misc/eshell.texi | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi index 99949815edd..51f7985825d 100644 --- a/doc/lispref/objects.texi +++ b/doc/lispref/objects.texi @@ -2407,7 +2407,7 @@ that is evaluated. For example: @noindent Although the list @code{(0.5)} was mutable when it was created, it should not -have been changed via @code{setcar} because it given to @code{eval}. The +have been changed via @code{setcar} because it was given to @code{eval}. The reverse does not occur: an object that should not be changed never becomes mutable afterwards. diff --git a/doc/misc/eshell.texi b/doc/misc/eshell.texi index 0d3d3891501..66f54137505 100644 --- a/doc/misc/eshell.texi +++ b/doc/misc/eshell.texi @@ -512,8 +512,8 @@ below the @code{completion-cycle-threshold}), press @kbd{M-?}. @subsection pcomplete Pcomplete, short for programmable completion, is the completion library originally written for Eshell, but usable for command -completion@footnote{Command completion as opposed to code completion, -which is a beyond the scope of pcomplete.} in other modes. +completion@footnote{Command completion, as opposed to code completion, +which is beyond the scope of pcomplete.} in other modes. Completions are defined as functions (with @code{defun}) named @code{pcomplete/COMMAND}, where @code{COMMAND} is the name of the |