17beafee7d45

--- a/src/wam/compiler.lisp	Sun Jun 05 00:01:11 2016 +0000
+++ b/src/wam/compiler.lisp	Sun Jun 05 00:06:51 2016 +0000
@@ -562,7 +562,7 @@
 ;;; A quick note on cut (!): the book and original WAM do some nutty things to
 ;;; save one stack word per frame.  They store the cut register for non-neck
 ;;; cuts in a "pseudovariable" on the stack, so they only have to allocate that
-;;; extra stack word for things that actually *use* non-neck cuts
+;;; extra stack word for things that actually *use* non-neck cuts.
 ;;;
 ;;; We're going to just eat the extra stack word and store the cut register in
 ;;; every frame instead.  This massively simplifies the implementation and lets

--- a/src/wam/vm.lisp	Sun Jun 05 00:01:11 2016 +0000
+++ b/src/wam/vm.lisp	Sun Jun 05 00:06:51 2016 +0000
@@ -136,7 +136,7 @@
     (loop
       ;; The book is, yet again, fucked.  It just sets `i` to be the trail
       ;; pointer from the choice point frame.  But what if we just popped off
-      ;; the last choice point?  If that's the case We need to look over the
+      ;; the last choice point?  If that's the case we need to look over the
       ;; entire trail.
       :with i = (if (wam-backtrack-pointer-unset-p wam b)
                   0