Index: doc/papers/general/Paper.tex
===================================================================
--- doc/papers/general/Paper.tex	(revision e6e344569fc9081a8886ab65d5c710cbda3bfc79)
+++ doc/papers/general/Paper.tex	(revision c4d4ecf2236c625c2cb2120b42a876a14cc53dff)
@@ -1114,10 +1114,10 @@
 \end{cfa}
 \CFA allows the declaration of local variables, \eg @y@, at the start of the @switch@ with scope across the entire @switch@ body, \ie all @case@ clauses, but no statements.
-\CFA disallows the declaration of local variable, \eg @z@, within the @switch@ body, because a declaration cannot occur immediately after a @case@ since a label can only be attached to a statement, and the use of @z@ is undefined in @case 1@ as neither storage allocation nor initialization may have occurred.
+\CFA disallows the declaration of local variable, \eg @z@, directly within the @switch@ body, because a declaration cannot occur immediately after a @case@ since a label can only be attached to a statement, and the use of @z@ is undefined in @case 1@ as neither storage allocation nor initialization may have occurred.
 
 C @switch@ provides multiple entry points into the statement body, but once an entry point is selected, control continues across \emph{all} @case@ clauses until the end of the @switch@ body, called \newterm{fall through}.
 @case@ clauses are made disjoint by the @break@ statement.
 While the ability to fall through \emph{is} a useful form of control flow, it does not match well with programmer intuition, resulting in many errors from missing @break@ statements.
-\CFA provides a new control structure, @choose@ that mimics the @switch@, but reverses the meaning of fall through:
+\CFA provides a new control structure, @choose@, which mimics @switch@, but reverses the meaning of fall through:
 \begin{cquote}
 \lstDeleteShortInline@%
@@ -1126,5 +1126,5 @@
 \begin{cfa}
 `choose` ( day ) {
-  case Mon, Tue, Wed, Thu:
+  case Mon~Thu:
 	// program