[Guile-commits] 01/01: Language fix

[Mikael Djurfeldt]

mdj pushed a commit to branch master
in repository guile.

commit 52398d1db42a0fa9f367dbc3f8f33c592d01f76f
Author: Mikael Djurfeldt <address@hidden>
Date:   Mon Oct 29 16:00:44 2018 +0100

    Language fix
    
    * doc/ref/vm.texi: Fix bad sentence.
---
 doc/ref/vm.texi | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/doc/ref/vm.texi b/doc/ref/vm.texi
index 44220a0..4eb327f 100644
--- a/doc/ref/vm.texi
+++ b/doc/ref/vm.texi
@@ -424,15 +424,15 @@ involved making an object (@code{ip} 3), putting a code 
pointer in it
 (@code{ip} 11).
 
 The second stanza disassembles the code for the closure.  After the
-prelude, all of the code between @code{ip} 5 and 24 related to loading
-the load the variable for the toplevel variable @code{foo} into slot 1.
-This lookup happens only once, and is associated with a cache; after the
-first run, the value in the cache will be a bound variable, and the code
-will jump from @code{ip} 7 to 26.  On the first run, Guile gets the
-module associated with the function, calls out to a run-time routine to
-look up the variable, and checks that the variable is bound before
-initializing the cache.  Either way, @code{ip} 26 dereferences the
-variable into local 2.
+prelude, all of the code between @code{ip} 5 and 24 is related to
+loading the toplevel variable @code{foo} into slot 1.  This lookup
+happens only once, and is associated with a cache; after the first run,
+the value in the cache will be a bound variable, and the code will jump
+from @code{ip} 7 to 26.  On the first run, Guile gets the module
+associated with the function, calls out to a run-time routine to look up
+the variable, and checks that the variable is bound before initializing
+the cache.  Either way, @code{ip} 26 dereferences the variable into
+local 2.
 
 What follows is the allocation and initialization of the vector return
 value.  @code{Ip} 27 does the allocation, and the following two