summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2005-07-18 08:04:17 (GMT)
committerGeorg Brandl <georg@python.org>2005-07-18 08:04:17 (GMT)
commit298225245242f00989032acc5e015a7dbabe83d8 (patch)
tree7aabec247e67c0a1e4ee77a95e10ac4b03421583
parentca5feabac2a060122d8e3aac1d889e9f0a6c85e2 (diff)
downloadcpython-298225245242f00989032acc5e015a7dbabe83d8.zip
cpython-298225245242f00989032acc5e015a7dbabe83d8.tar.gz
cpython-298225245242f00989032acc5e015a7dbabe83d8.tar.bz2
bug [ 850238 ] unclear documentation/missing command?
-rw-r--r--Doc/doc/doc.tex6
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/doc/doc.tex b/Doc/doc/doc.tex
index ebebd91..e4b91ac 100644
--- a/Doc/doc/doc.tex
+++ b/Doc/doc/doc.tex
@@ -1134,9 +1134,9 @@ verbatim
\subsection{Module-specific Markup \label{module-markup}}
The markup described in this section is used to provide information
- about a module being documented. A typical use of this markup
- appears at the top of the section used to document a module. A
- typical example might look like this:
+ about a module being documented. Each module should be documented
+ in its own \macro{section}. A typical use of this markup
+ appears at the top of that section and might look like this:
\begin{verbatim}
\section{\module{spam} ---