make tech links gray; fix-ups in reference manual

svn: r10430

collects/scribble/scribble.css

@@ -439,7 +439,7 @@ i {
 
 .techlink {
   text-decoration: none;
-  color: black;
+  color: #606060;
 }
 
 .techlink:hover {

collects/scribblings/foreign/derived.scrbl

@@ -54,7 +54,7 @@ too. The @scheme[_id] must start with @litchar{_}.
 The optional expression produces optional arguments to @scheme[_cpointer].
 
 In addition to defining @scheme[_id] to a type generated by
-@scheme[_cpointer], @scheme[_foo]@schemeidfont{/null} is bound to a
+@scheme[_cpointer], @scheme[_id]@schemeidfont{/null} is bound to a
 type produced by @scheme[_cpointer/null] type. Finally,
 @schemevarfont{id}@schemeidfont{?}  is defined as a predicate, and
 @schemevarfont{id}@schemeidfont{-tag} is defined as an accessor to
@@ -77,10 +77,10 @@ possible to construct pointer types that can be treated as other
 pointer types, mainly for implementing inheritance via upcasts (when a
 struct contains a super struct as its first element).
 
-The @scheme[cpointer-hash-tag] function checks whether if the given
+The @scheme[cpointer-has-tag?] function checks whether if the given
 @scheme[cptr] has the @scheme[tag]. A pointer has a tag @scheme[tag]
 when its tag is either @scheme[eq?] to @scheme[tag] or a list that
-contains (@scheme[memq]) @scheme[t].
+contains (in the sense of @scheme[memq]) @scheme[tag].
 
 The @scheme[cpointer-push-tag!] function pushes the given @scheme[tag]
 value on @scheme[cptr]'s tags.  The main properties of this operation
@@ -95,8 +95,8 @@ a single-element list).}
 
 @section[#:tag "foreign:cvector"]{Safe C Vectors}
 
-The @scheme[cvector] form can be used as a type C vectors (i.e., a the
-pointer to the memory block).
+The @scheme[cvector] form can be used as a type C vectors (i.e., a
+pointer to a memory block).
 
 @defproc[(make-cvector [type ctype?][length exact-nonnegative-integer?]) cvector?]{
 

collects/scribblings/mzc/api.scrbl

@@ -84,7 +84,7 @@ collection.  The following fields are used:
        effectively ignore the collection for
        compilation). Automatically omitted files and directories are
        @filepath{compiled}, @filepath{doc}, and those whose names
-       start with @litchar{.}
+       start with @litchar{.}.
 
        Files that are required by other files, however, are always
        compiled in the process of compiling the requiring file---even

collects/scribblings/reference/define-struct.scrbl

@@ -101,7 +101,13 @@ information on these attributes of a structure type.  The
 multiple times, attaches a property value to the structure type; see
 @secref["structprops"] for more information on properties. The
 @scheme[#:transparent] option is a shorthand for @scheme[#:inspector
-#f]. 
+#f].
+
+@margin-note{Use the @scheme[prop:procedure] to property implement an
+@as-index{applicable structure}, use @scheme[prop:evt] to create a
+structure type whose instances are @tech{synchronizable events}, and
+so on. By convention, property names usually start with
+@schemeidfont{prop:}.}
 
 The @scheme[#:prefab] option obtains a @techlink{prefab} (pre-defined,
 globally shared) structure type, as opposed to creating a new

collects/scribblings/reference/eval-model.scrbl

@@ -606,7 +606,7 @@ to implement dynamic scope.
 @section[#:tag "prompt-model"]{Prompts, Delimited Continuations, and Barriers}
 
 A @deftech{prompt} is a special kind of continuation frame that is
-annotated with a specific @deftech{prompt-tag} (essentially a
+annotated with a specific @deftech{prompt tag} (essentially a
 continuation mark). Various operations allow the capture of frames in
 the continuation from the redex position out to the nearest enclosing
 prompt with a particular prompt tag; such a continuation is sometimes
@@ -661,14 +661,15 @@ is created) as all other threads.
 @section[#:tag "parameter-model"]{Parameters}
 
 @deftech{Parameters} are essentially a derived concept in Scheme; they
-are defined in terms of continuation marks and thread cells. However,
-parameters are also built in, in the sense that some primitive
-procedures consult parameter values. For example, the default output
-stream for primitive output operations is determined by a parameter.
+are defined in terms of @tech{continuation marks} and @tech{thread
+cells}. However, parameters are also built in, in the sense that some
+primitive procedures consult parameter values. For example, the
+default output stream for primitive output operations is determined by
+a parameter.
 
 A parameter is a setting that is both thread-specific and
 continuation-specific. In the empty continuation, each parameter
-corresponds to a preserved thread cell; a corresponding
+corresponds to a @tech{preserved} @tech{thread cell}; a corresponding
 @deftech{parameter procedure} accesses and sets the thread cell's
 value for the current thread.
 
@@ -692,19 +693,19 @@ are defined in terms of continuations, prompts, and continuation
 marks.  However, exceptions are also built in, in the sense that
 primitive forms and procedures may raise exceptions.
 
-A handler for uncaught exceptions is designated through a built-in
-parameter. A handler to catch exceptions can be associated with a
-continuation frame though a continuation mark (whose key is not
-directly accessible). When an exception is raised, the current
-continuation's marks determine a chain of handler procedures that are
-consulted to handle the exception.
+An @deftech{exception handler} to catch exceptions can be associated
+with a continuation frame though a @tech{continuation mark} (whose key
+is not directly accessible). When an exception is raised, the current
+continuation's marks determine a chain of @tech{exception handler}
+procedures that are consulted to handle the exception. A handler for
+uncaught exceptions is designated through a built-in @tech{parameter}.
 
-One potential action of an exception handler is to abort the current
-continuation up to an enclosing prompt with a particular tag.  The
-default handler for uncaught exceptions, in particular, aborts to a
-particular tag for which a prompt is always present, because the
-prompt is installed in the outermost frame of the continuation for any
-new thread.
+One potential action of an @tech{exception handler} is to abort the
+current @tech{continuation} up to an enclosing @tech{prompt} with a
+particular @tech{prompt tag}.  The default handler for uncaught
+exceptions, in particular, aborts to a particular tag for which a
+prompt is always present, because the prompt is installed in the
+outermost frame of the continuation for any new thread.
 
 @;------------------------------------------------------------------------
 @section[#:tag "custodian-model"]{Custodians}

collects/scribblings/reference/exns.scrbl

@@ -10,12 +10,12 @@ model. It is based on a proposal by Friedman, Haynes, and Dybvig
 
 Whenever a primitive error occurs in PLT Scheme, an exception is
 raised.  The value that is passed to the current @tech{exception
-handler} is always an instance of the @scheme[exn] structure
-type. Every @scheme[exn] structure value has a @scheme[message] field
-that is a string, the primitive error message.  The default exception
-handler recognizes exception values with the @scheme[exn?] predicate
-and passes the error message to the current error display handler (see
-@scheme[error-display-handler]).
+handler} for a primitive error is always an instance of the
+@scheme[exn] structure type. Every @scheme[exn] structure value has a
+@scheme[message] field that is a string, the primitive error message.
+The default exception handler recognizes exception values with the
+@scheme[exn?] predicate and passes the error message to the current
+error display handler (see @scheme[error-display-handler]).
 
 Primitive procedures that accept a procedure argument with a
 particular required arity (e.g., @scheme[call-with-input-file],
@@ -29,7 +29,7 @@ particular required arity (e.g., @scheme[call-with-input-file],
 
 Raises an exception, where @scheme[v] represents the exception being
 raised. The @scheme[v] argument can be anything; it is passed to the
-current @deftech{exception handler}.
+current @tech{exception handler}.
 
 If @scheme[barrier?] is true, then the call to the @tech{exception
 handler} is protected by a @tech{continuation barrier}, so that