diff --git a/S02-bits.pod b/S02-bits.pod
index 4e024497b..24612cd24 100644
--- a/S02-bits.pod
+++ b/S02-bits.pod
@@ -8,8 +8,8 @@ Synopsis 2: Bits and Pieces
 
     Created: 10 Aug 2004
 
-    Last Modified: 10 Apr 2015
-    Version: 293
+    Last Modified: 21 Apr 2015
+    Version: 294
 
 This document summarizes Apocalypse 2, which covers small-scale lexical
 items and typological issues.  (These Synopses also contain updates to
@@ -2720,11 +2720,14 @@ coyotes.)
 The file's scope is known as C<UNIT>, but there are one or more lexical
 scopes outside of that corresponding to the linguistic setting (often known
 as the prelude in other cultures).  Hence, the C<SETTING> scope is
-equivalent to C<UNIT::OUTER>.  For a standard Perl program C<SETTING> is the
+equivalent to C<UNIT::OUTERS>.  For a standard Perl program C<SETTING> is the
 same as C<CORE>, but various startup options (such as C<-n> or C<-p>) can
 put you into a domain specific language, in which case C<CORE> remains the
 scope of the standard language, while C<SETTING> represents the scope
-defining the DSL that functions as the setting of the current file.  See
+defining the DSL that functions as the setting of the current file.  When used
+as a search term in the middle of a name, C<SETTING> includes all its outer scopes
+up to C<CORE>.  To get I<only> the setting's outermost scope, use C<UNIT::OUTER> instead.
+See
 also the C<-L>/C<--language> switch described in L<S19>.  If a setting
 wishes to gain control of the main execution, it merely needs to declare a
 C<MAIN> routine as documented in S06.  In this case the ordinary execution