summaryrefslogtreecommitdiff
path: root/doc/lispref
diff options
context:
space:
mode:
Diffstat (limited to 'doc/lispref')
-rw-r--r--doc/lispref/macros.texi2
-rw-r--r--doc/lispref/variables.texi2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/lispref/macros.texi b/doc/lispref/macros.texi
index dca88d2b7c7..de9e1c405f0 100644
--- a/doc/lispref/macros.texi
+++ b/doc/lispref/macros.texi
@@ -605,7 +605,7 @@ either.
Within a macro definition, you can use the @code{declare} form
(@pxref{Defining Macros}) to specify how to @key{TAB} should indent
-calls to the macro. An indentation specifiction is written like this:
+calls to the macro. An indentation specification is written like this:
@example
(declare (indent @var{indent-spec}))
diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi
index ab3a4edc0ac..94e71c96d0a 100644
--- a/doc/lispref/variables.texi
+++ b/doc/lispref/variables.texi
@@ -303,7 +303,7 @@ If a variable is void, trying to evaluate the variable signals a
Under lexical binding rules, the value cell only holds the
variable's global value, i.e.@: the value outside of any lexical
-binding contruct. When a variable is lexically bound, the local value
+binding construct. When a variable is lexically bound, the local value
is determined by the lexical environment; the variable may have a
local value if its symbol's value cell is unassigned.