diff --git a/doc/ref/data-rep.texi b/doc/ref/data-rep.texi
index 7099c87d0..23a1bb4bf 100644
--- a/doc/ref/data-rep.texi
+++ b/doc/ref/data-rep.texi
@@ -491,7 +491,7 @@ Before Guile 2.0, Guile had a custom garbage collector that allocated
 heap objects in units of 2-word @dfn{cells}.  With the move to the
 BDW-GC collector in Guile 2.0, Guile can allocate heap objects of any
 size, and the concept of a cell is now obsolete.  Still, we mention
-it here as the name stil appears in various low-level interfaces.
+it here as the name still appears in various low-level interfaces.
 
 @deftypefn Macro {scm_t_bits *} SCM_UNPACK_POINTER (SCM @var{x})
 @deftypefnx Macro {scm_t_cell *} SCM2PTR (SCM @var{x})
diff --git a/doc/ref/vm.texi b/doc/ref/vm.texi
index 66fda17bf..44220a0c6 100644
--- a/doc/ref/vm.texi
+++ b/doc/ref/vm.texi
@@ -16,7 +16,7 @@ high-level code to low-level code.  Sometimes these languages are
 implemented using compilers:  programs that translate high-level
 programs to equivalent low-level code, and pass on that low-level code
 to some other language implementation.  Each of these languages can be
-throught to be virtual machines: they offer programs an abstract machine
+thought to be virtual machines: they offer programs an abstract machine
 on which to run.
 
 Guile implements a number of interpreters and compilers on different
@@ -86,7 +86,7 @@ needs (tail calls, multiple values, @code{call/cc}) and can provide
 optimized inline instructions for Guile as well (GC-managed allocations,
 type checks, etc.).
 
-Guie also includes a just-in-time (JIT) compiler to translate bytecode
+Guile also includes a just-in-time (JIT) compiler to translate bytecode
 to native code.  Because Guile uses the portable GNU Lightning library
 to emit that code, we keep the benefits of portability while also
 benefitting from fast native code.  To avoid too much time spent in the