Finish CPS documentation

[bpt/guile.git] / doc / ref / api-evaluation.texi

diff --git a/doc/ref/api-evaluation.texi b/doc/ref/api-evaluation.texi
index f0edd11..1810fe8 100644 (file)
--- a/doc/ref/api-evaluation.texi
+++ b/doc/ref/api-evaluation.texi
@@ -664,13 +664,13 @@ Use @var{lang} as the source language of @var{file}.  If this option is omitted,
 @item -t @var{lang}
 @itemx --to=@var{lang}
 Use @var{lang} as the target language of @var{file}.  If this option is omitted,
-@code{objcode} is assumed.
+@code{rtl} is assumed.
 
 @item -T @var{target}
 @itemx --target=@var{target}
-Produce bytecode for @var{target} instead of @var{%host-type}
-(@pxref{Build Config, %host-type}).  Target must be a valid GNU triplet,
-such as @code{armv5tel-unknown-linux-gnueabi} (@pxref{Specifying Target
+Produce code for @var{target} instead of @var{%host-type} (@pxref{Build
+Config, %host-type}).  Target must be a valid GNU triplet, such as
+@code{armv5tel-unknown-linux-gnueabi} (@pxref{Specifying Target
 Triplets,,, autoconf, GNU Autoconf Manual}).
 
 @end table
@@ -695,7 +695,7 @@ the Virtual Machine}.
 @end deffn
 
 @deffn {Scheme Procedure} compile-file file [#:output-file=#f] @
-                          [#:from=(current-language)] [#:to='objcode] @
+                          [#:from=(current-language)] [#:to='rtl] @
                           [#:env=(default-environment from)] @
                           [#:opts='()] @
                           [#:canonicalization='relative]
@@ -924,8 +924,8 @@ When @code{primitive-load-path} searches the @code{%load-compiled-path}
 for a corresponding compiled file for a relative path it does so by
 appending @code{.go} to the relative path.  For example, searching for
 @code{ice-9/popen} could find
-@code{/usr/lib/guile/2.0/ccache/ice-9/popen.go}, and use it instead of
-@code{/usr/share/guile/2.0/ice-9/popen.scm}.
+@code{/usr/lib/guile/2.2/ccache/ice-9/popen.go}, and use it instead of
+@code{/usr/share/guile/2.2/ice-9/popen.scm}.
 
 If @code{primitive-load-path} does not find a corresponding @code{.go}
 file in the @code{%load-compiled-path}, or the @code{.go} file is out of
@@ -1167,7 +1167,7 @@ it contains, splicing them into the location of the @code{include},
 within a @code{begin}.
 
 If @var{file-name} is a relative path, it is searched for relative to
-the path that contains the file that the @code{include} for appears in.
+the path that contains the file that the @code{include} form appears in.
 @end deffn
 
 If you are a C programmer, if @code{load} in Scheme is like