\end{verbatim}
This function must be registered with the interpreter using the
-\constant{METH_VARARGS} flag; this is described in Section
+\constant{METH_VARARGS} flag; this is described in section
\ref{methodTable}, ``The Module's Method Table and Initialization
Function.'' The \cfunction{PyArg_ParseTuple()} function and its
-arguments are documented in Section \ref{parseTuple}, ``Format Strings
+arguments are documented in section \ref{parseTuple}, ``Format Strings
for \cfunction{PyArg_ParseTuple()}.''
The macros \cfunction{Py_XINCREF()} and \cfunction{Py_XDECREF()}
increment/decrement the reference count of an object and are safe in
the presence of \NULL{} pointers (but note that \var{temp} will not be
-\NULL{} in this context). More info on them in Section
+\NULL{} in this context). More info on them in section
\ref{refcounts}, ``Reference Counts.''
Later, when it is time to call the function, you call the C function
\index{Font Manager, IRIS}
\index{IRIS Font Manager}
It is available only on Silicon Graphics machines.
-See also: \emph{4Sight User's Guide}, Section 1, Chapter 5: ``Using
+See also: \emph{4Sight User's Guide}, section 1, chapter 5: ``Using
the IRIS Font Manager.''
This is not yet a full interface to the IRIS Font Manager.
File objects are implemented using \C{}'s \code{stdio}
package and can be created with the built-in function
-\function{open()}\bifuncindex{open} described Section
+\function{open()}\bifuncindex{open} described section
\ref{built-in-funcs}, ``Built-in Functions.'' They are also returned
by some other built-in functions and methods, e.g.,
\function{posix.popen()} and \function{posix.fdopen()} and the