From: Matt Birkholz Date: Fri, 16 Mar 2018 20:24:08 +0000 (-0700) Subject: doc/user-manual/user.texinfo: random wordsmithing X-Git-Tag: mit-scheme-pucked-x11-0.2.2~35 X-Git-Url: https://birchwood-abbey.net/git?a=commitdiff_plain;h=6a005d6f3a9dd767bcc5fe87373e729b6b4af24c;p=mit-scheme.git doc/user-manual/user.texinfo: random wordsmithing --- diff --git a/doc/user-manual/user.texinfo b/doc/user-manual/user.texinfo index 15573de83..c1d5b389e 100644 --- a/doc/user-manual/user.texinfo +++ b/doc/user-manual/user.texinfo @@ -3844,8 +3844,8 @@ strange name, the core of the system is largely unchanged. The core of MIT/GNU Scheme Pucked is the @emph{bleeding edge core}. The head of the MIT/GNU Scheme project's development branch on -Savannah is merged in frequently. Thus it includes changes proposed -for the next stable release of MIT/GNU Scheme. +Savannah is merged in frequently, so this version includes changes +proposed for the next stable release of MIT/GNU Scheme. @itemize @bullet @item @@ -3877,8 +3877,8 @@ them in your packaging construction reports (@file{.crf} files). New unicode support means your old code can generate ``legacy strings'' suitable only for ``legacy ports''. Most string operations can handle legacy @emph{or} Unicode strings, but new procedures may -only handle Unicode strings, and several old procedures are marked as -``deprecated.'' +only handle Unicode strings, and several old procedures are marked +deprecated. @end itemize The proposed changes to the core system are intended to produce a new @@ -3886,7 +3886,7 @@ release compatible with the current release. The new release will support both parameters and fluid bound bindings, both legacy and Unicode strings. It should thus be possible to run mixtures of old and new code, allowing you to replace references to deprecated -bindings in stages. +bindings incrementally. @section Experimental Changes @@ -4026,7 +4026,7 @@ Using an Ubuntu package manager, you can add Birchwood Abbey to your list of package sources and install or update Scheme and its plugins just like other packages. -You should begin by installing the GPG key used to sign the packages. +You would begin by installing the GPG key used to sign the packages. It is available at this URL: @example