minor documentation fixes

csug/libraries.stex

@@ -1024,7 +1024,7 @@ automatically calls the value of the \scheme{compile-library-handler} parameter
 to a procedure that simply calls \scheme{compile-library}) on any imported library if
 the object file is missing, older than the corresponding source file,
 older than any source files included (via \index{\scheme{include}}\scheme{include}) when the
-object file was created, or itself requires a library that has or must
+object file was created, or itself requires a library that has been or must
 be recompiled, as described in Section~\ref{SECTUSELIBRARIES}.
 The default initial value of this parameter is \scheme{#f}.
 It can be set to \scheme{#t} via the command-line option

csug/system.stex

@@ -2902,7 +2902,7 @@ the parameter \scheme{generate-profile-forms} can be set to \scheme{#f}
 to inhibit the expander's implicit generation of \scheme{profile} forms
 for all annotated source expressions.
 It is also possible to obtain finer control over implicit generation of
-\scheme{profile} forms by marking which annotations that should and
+\scheme{profile} forms by marking which annotations should and
 should not be used for profiling (Section~\ref{SECTSYNTAXANNOTATIONS}).
 
 With block profiling enabled, the compiler similarly instruments the

csug/use.stex

@@ -1223,7 +1223,8 @@ control parameters are described in Section~\ref{SECTSMGMTGC}.
 \index{profiling}%
 Finally, it is often useful to ``profile'' your code to determine that
 parts of the code that are executed most frequently.
-While this will not help the system optimize your code, it can help
+While this may help the system optimize your code, the primary
+benefit is to help
 you identify ``hot spots'' where you need to concentrate your own
 hand-optimization efforts.
 In these hot spots, consider using more efficient operators, like
@@ -1235,7 +1236,7 @@ These operators can make code more readable when used judiciously,
 but they can slow down time-critical code.
 
 Section~\ref{SECTMISCPROFILE} describes how to use the compiler's support
-for automatic profiling.
+for automatic profiling and profile-directed optimization.
 Be sure that profiling is not enabled when you compile your production
 code, since the code introduced into the generated code to perform the
 profiling adds significant run-time overhead.

release_notes/release_notes.stex

@@ -71,14 +71,14 @@ creating a syntactic binding for one of the built-in types, such as
 As of 9.5.8, syntactic bindings that do not bind an ftype descriptor are no
 longer considered when defining ftypes.
 
-This change also allows a base ftype to be bound using `define-ftype`, though
+This change also allows a base ftype to be bound using \scheme{define-ftype}, though
 this fixes the endianness of the type.  For instance:
 
 \schemedisplay
 (define-ftype integer-32 integer-32)
 \endschemedisplay
 
-This binds the ftype `integer-32` to the native-endian `integer-32`.  It is possible to bind both endiannesses by using explicit names:
+This binds the ftype \scheme{integer-32} to the native-endian \scheme{integer-32}.  It is possible to bind both endiannesses by using explicit names:
 
 \schemedisplay
 (define-ftype integer-32-be (endian big integer-32))