add a constant string "boot-source" which is run at startup

this will allow us to have compiled-in code that wouldn't run under the transforms, though we don't add anything of substance just yet

this strategy was used early in bring-up, in the historical flatassembler version of Evocation, so the design space of it is already well-explored in Irenes' head. how pleasant. :)

Force-Push: yes
Change-Id: I722cddb77657df9ca518c0d9841aa587bf63feb3

1 files changed, 4 insertions, 4 deletions

diff --git a/README.txt b/README.txt
index ce7a254..8657dc6 100644
--- a/README.txt
+++ b/README.txt
@@ -245,10 +245,10 @@ expectations on yourself around understanding the transformation facility.
 
   It's okay, you can benefit from it before you understand it: Transformation
 provides the core tricks that make it possible to compile Forth code into
-standalone executables. The call to label-transform in evoke.e, and the call
-to log-load-transform in compilation/execution.e, are the two spots where
-compilation is handed off to the transformation facility, and you can pretty
-much just take it for granted that it works, until you feel ready.
+standalone executables. The calls to label-transform and log-load-transform in
+evoke.e are the two spots where compilation is handed off to the
+transformation facility, and you can pretty much just take it for granted that
+it works, until you feel ready.
 
   If you want examples of programs that are smaller than Evocation itself,
 quine.e is a tiny program written in proper Evocation that outputs its own