summaryrefslogtreecommitdiffstats
path: root/Doc/dist/dist.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Doc/dist/dist.tex')
-rw-r--r--Doc/dist/dist.tex6
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/dist/dist.tex b/Doc/dist/dist.tex
index d01e1fd..e06b887 100644
--- a/Doc/dist/dist.tex
+++ b/Doc/dist/dist.tex
@@ -34,7 +34,7 @@
build/release/install mechanics.
\end{abstract}
-% The ugly "%begin{latexonly}" pseudo-environment supresses the table
+% The ugly "%begin{latexonly}" pseudo-environment suppresses the table
% of contents for HTML generation.
%
%begin{latexonly}
@@ -965,7 +965,7 @@ inplace=1
\end{verbatim}
This will affect all builds of this module distribution, whether or not
-you explcitly specify \command{build\_ext}. If you include
+you explicitly specify \command{build\_ext}. If you include
\file{setup.cfg} in your source distribution, it will also affect
end-user builds---which is probably a bad idea for this option, since
always building extensions in-place would break installation of the
@@ -2521,7 +2521,7 @@ output debug symbols in (or alongside) the object file(s).
\var{extra_preargs} and \var{extra_postargs} are implementation- dependent.
On platforms that have the notion of a command-line (e.g. \UNIX,
DOS/Windows), they are most likely lists of strings: extra
-command-line arguments to prepand/append to the compiler command
+command-line arguments to prepend/append to the compiler command
line. On other platforms, consult the implementation class
documentation. In any event, they are intended as an escape hatch
for those occasions when the abstract compiler framework doesn't