When referring to namespaces, always say "namespaces" instead of

"name spaces".

Inconsistency noted by Keith Briggs <keith.briggs@bt.com>.

Doc/lib/libdis.tex

@@ -480,9 +480,9 @@ in \code{cmp_op[\var{opname}]}.
 
 \begin{opcodedesc}{IMPORT_NAME}{namei}
 Imports the module \code{co_names[\var{namei}]}.  The module object is
-pushed onto the stack.  The current name space is not affected: for a
+pushed onto the stack.  The current namespace is not affected: for a
 proper import statement, a subsequent \code{STORE_FAST} instruction
-modifies the name space.
+modifies the namespace.
 \end{opcodedesc}
 
 \begin{opcodedesc}{IMPORT_FROM}{namei}

Doc/lib/libfuncs.tex

@@ -227,7 +227,7 @@ class instances are callable if they have a \method{__call__()} method.
   The arguments are a file name and two optional dictionaries.  The
   file is parsed and evaluated as a sequence of Python statements
   (similarly to a module) using the \var{globals} and \var{locals}
-  dictionaries as global and local name space.  If the \var{locals}
+  dictionaries as global and local namespace.  If the \var{locals}
   dictionary is omitted it defaults to the \var{globals} dictionary.
   If both dictionaries are omitted, the expression is executed in the
   environment where \function{execfile()} is called.  The return value is

Doc/lib/libstdtypes.tex

@@ -888,7 +888,7 @@ different object types.
 The implementation adds two special read-only attributes:
 \code{\var{f}.func_code} is a function's \dfn{code
 object}\obindex{code} (see below) and \code{\var{f}.func_globals} is
-the dictionary used as the function's global name space (this is the
+the dictionary used as the function's global namespace (this is the
 same as \code{\var{m}.__dict__} where \var{m} is the module in which
 the function \var{f} was defined).