scribble style (capitalize section names)

collects/syntax/scribblings/parse.scrbl

@@ -2,7 +2,7 @@
 @(require scribble/manual
           (for-label syntax/parse))
 
-@title[#:tag "stxparse" #:style '(toc)]{Parsing and specifying syntax}
+@title[#:tag "stxparse" #:style '(toc)]{Parsing and Specifying Syntax}
 
 The @racketmodname[syntax/parse] library provides a framework for
 writing macros and processing syntax. The library provides a powerful

collects/syntax/scribblings/parse/debug.scrbl

@@ -5,7 +5,7 @@
           scribble/eval
           "parse-common.rkt")
 
-@title{Debugging and inspection tools}
+@title{Debugging and Inspection Tools}
 
 @defmodule[syntax/parse/debug]
 

collects/syntax/scribblings/parse/define.scrbl

@@ -6,7 +6,7 @@
           "parse-common.rkt"
           (for-label syntax/parse/define))
 
-@title{Defining simple macros}
+@title{Defining Simple Macros}
 
 @defmodule[syntax/parse/define]
 

collects/syntax/scribblings/parse/ex-exprc.scrbl

@@ -6,7 +6,7 @@
           "parse-common.rkt"
           (for-label racket/class))
 
-@title[#:tag "exprc"]{Contracts on macro sub-expressions}
+@title[#:tag "exprc"]{Contracts on Macro Sub-expressions}
 
 Just as procedures often expect certain kinds of values as arguments,
 macros often have expectations about the expressions they are

collects/syntax/scribblings/parse/ex-kw-args.scrbl

@@ -6,7 +6,7 @@
           "parse-common.rkt"
           (for-label racket/class))
 
-@title{Optional keyword arguments}
+@title{Optional Keyword Arguments}
 
 This section explains how to write a macro that accepts (simple)
 optional keyword arguments. We use the example @racket[mycond], which

collects/syntax/scribblings/parse/ex-many-kws.scrbl

@@ -6,7 +6,7 @@
           "parse-common.rkt"
           (for-label racket/class))
 
-@title{More keyword arguments}
+@title{More Keyword Arguments}
 
 This section shows how to express the syntax of @racket[struct]'s
 optional keyword arguments using @racket[syntax-parse] patterns.

collects/syntax/scribblings/parse/ex-mods-stxclasses.scrbl

@@ -6,7 +6,7 @@
           "parse-common.rkt"
           (for-label racket/class))
 
-@title{Modules and reusable syntax classes}
+@title{Modules and Reusable Syntax Classes}
 
 As demonstrated in the @secref{stxparse-intro}, the simplest place to
 define a syntax class is within the macro definition that uses it. But

collects/syntax/scribblings/parse/ex-uniform.scrbl

@@ -6,7 +6,7 @@
           "parse-common.rkt"
           (for-label racket/class))
 
-@title[#:tag "uniform-meanings"]{Variants with uniform meanings}
+@title[#:tag "uniform-meanings"]{Variants with Uniform Meanings}
 
 Syntax classes not only validate syntax, they also extract some
 measure of meaning from it. From the perspective of meaning, there are

collects/syntax/scribblings/parse/ex-varied.scrbl

@@ -6,7 +6,7 @@
           "parse-common.rkt"
           (for-label racket/class))
 
-@title[#:tag "varied-meanings"]{Variants with varied meanings}
+@title[#:tag "varied-meanings"]{Variants with Varied Meanings}
 
 As explained in the @seclink["uniform-meanings"]{previous section},
 the meaning of a syntax class can be uniform, or it can be varied;
@@ -35,7 +35,7 @@ enter a new scope'' case.
 This section discusses two ways of representing varied kinds of
 information.
 
-@section{Syntactic normalization}
+@section{Syntactic Normalization}
 
 One approach is based on the observation that the syntactic variants
 already constitute a representation of the information they carry. So
@@ -68,7 +68,7 @@ A normalized syntactic representation is most useful when the
 subsequent case analysis is performed by @racket[syntax-parse] or a
 similar form.
 
-@section{Non-syntax-valued attributes}
+@section{Non-syntax-valued Attributes}
 
 When the information carried by the syntax is destined for complicated
 processing by Racket code, it is often better to parse it into an

collects/syntax/scribblings/parse/experimental.scrbl

@@ -9,14 +9,14 @@
 
 The following facilities are experimental.
 
-@section{Contracts for macro sub-expressions}
+@section{Contracts for Macro Sub-expressions}
 
 @defmodule[syntax/parse/experimental/contract]
 
 This module is deprecated; it reprovides @racket[expr/c] for backward
 compatibility.
 
-@section{Contracts for syntax classes}
+@section{Contracts for Syntax Classes}
 
 @defmodule[syntax/parse/experimental/provide]
 
@@ -152,7 +152,7 @@ Like @racket[~reflect] but for reified splicing syntax classes.
 
 @;{--------}
 
-@section{Procedural splicing syntax classes}
+@section{Procedural Splicing Syntax Classes}
 
 @defmodule[syntax/parse/experimental/splicing]
 
@@ -178,7 +178,7 @@ optional message argument.
 
 @;{--------}
 
-@section{Ellipsis-head alternative sets}
+@section{Ellipsis-head Alternative Sets}
 
 @defmodule[syntax/parse/experimental/eh]
 
@@ -242,7 +242,7 @@ their attributes with @racket[name].
 ]
 
 
-@section{Syntax class specialization}
+@section{Syntax Class Specialization}
 
 @defmodule[syntax/parse/experimental/specialize]
 

collects/syntax/scribblings/parse/lib.scrbl

@@ -6,9 +6,9 @@
           "parse-common.rkt"
           (for-label syntax/kerncase))
 
-@title{Library syntax classes and literal sets}
+@title{Library Syntax Classes and Literal Sets}
 
-@section{Syntax classes}
+@section{Syntax Classes}
 
 @(begin
    (define-syntax-rule (defstxclass name . pre-flows)
@@ -130,7 +130,7 @@ represents the checked expression.
 }
 
 
-@section{Literal sets}
+@section{Literal Sets}
 
 @defidform[kernel-literals]{
 

collects/syntax/scribblings/parse/litconv.scrbl

@@ -5,7 +5,7 @@
           scribble/eval
           "parse-common.rkt")
 
-@title{Literal sets and Conventions}
+@title{Literal Sets and Conventions}
 
 Sometimes the same literals are recognized in a number of different
 places. The most common example is the literals for fully expanded

collects/syntax/scribblings/parse/parsing.scrbl

@@ -5,7 +5,7 @@
           scribble/eval
           "parse-common.rkt")
 
-@title{Parsing syntax}
+@title{Parsing Syntax}
 
 This section describes @racket[syntax-parse], the
 @racketmodname[syntax/parse] library's facility for parsing

collects/syntax/scribblings/parse/patterns.scrbl

@@ -11,7 +11,7 @@
           (define def-dotsplus (defhere ...+))))
 @(define-dotsplus-names dotsplus def-dotsplus)
 
-@title[#:tag "stxparse-patterns"]{Syntax patterns}
+@title[#:tag "stxparse-patterns"]{Syntax Patterns}
 
 The grammar of @deftech{syntax patterns} used by
 @racketmodname[syntax/parse] facilities is given in the following
@@ -167,7 +167,7 @@ eh] pattern}
 
 @;{--------}
 
-@section{Single-term patterns}
+@section{Single-term Patterns}
 
 A @deftech{@Spattern} (abbreviated @svar[S-pattern]) is a pattern that
 describes a single term. These are like the traditional patterns used
@@ -587,7 +587,7 @@ ambiguity; it matches any term.
 }
 
 
-@section{Head patterns}
+@section{Head Patterns}
 
 A @deftech{@Hpattern} (abbreviated @svar[H-pattern]) is a pattern that
 describes some number of terms that occur at the head of some list
@@ -769,7 +769,7 @@ Matches a sequence of one element, which must be a term matching
 
 @;{--------}
 
-@section{Ellipsis-head patterns}
+@section{Ellipsis-head Patterns}
 
 An @deftech{@EHpattern} (abbreviated @svar[EH-pattern]) is pattern
 that describes some number of terms, like a @tech{@Hpattern}, but also
@@ -869,7 +869,7 @@ fails with the message either @racket[too-many-message-expr] or
 
 @;{--------}
 
-@section{Action patterns}
+@section{Action Patterns}
 
 An @deftech{@Apattern} (abbreviated @svar[A-pattern]) does not
 describe any syntax; rather, it has an effect such as the binding of

collects/syntax/scribblings/parse/stxclasses.scrbl

@@ -5,7 +5,7 @@
           scribble/eval
           "parse-common.rkt")
 
-@title[#:tag "stxparse-specifying"]{Specifying syntax with syntax classes}
+@title[#:tag "stxparse-specifying"]{Specifying Syntax with Syntax Classes}
 
 @declare-exporting[syntax/parse]
 
@@ -161,7 +161,7 @@ the pattern variables.
 
 @;{--------}
 
-@section{Pattern directives}
+@section{Pattern Directives}
 
 @section-index{pattern-directive}
 
@@ -255,7 +255,7 @@ in a @racket[#:do] block.
 
 @;{----------}
 
-@section{Pattern variables and attributes}
+@section{Pattern Variables and Attributes}
 
 An @deftech{attribute} is a name bound by a syntax pattern. An
 attribute can be a @tech{pattern variable} itself, or it can be a