GvR pointed out that only enclosing function bodies are part of nested scopes.

diff --git a/Doc/tut/tut.tex b/Doc/tut/tut.tex
index b7a909043de0fa3dfd704c2f4972d52b86de2dc9..6f7d22ec41910bf277d2e8b2cda6cec36f31f071 100644 (file)
--- a/Doc/tut/tut.tex
+++ b/Doc/tut/tut.tex
@@ -3553,11 +3553,11 @@ the namespace.
 Although scopes are determined statically, they are used dynamically.
 At any time during execution, there are at least three nested scopes whose
 namespaces are directly accessible: the innermost scope, which is searched
-first, contains the local names; the namespaces of any enclosing code
-blocks (a module, function, or class definition) which are searched starting
-with the nearest enclosing scope; the middle scope, searched next, contains
-the current module's global names; and the outermost scope (searched last)
-is the namespace containing built-in names.
+first, contains the local names; the namespaces of any enclosing
+functions, which are searched starting with the nearest enclosing scope;
+the middle scope, searched next, contains the current module's global names;
+and the outermost scope (searched last) is the namespace containing built-in
+names.
 
 If a name is declared global, then all references and assignments go
 directly to the middle scope containing the module's global names.