summaryrefslogtreecommitdiffstats
path: root/doc/binary.n
diff options
context:
space:
mode:
authordkf <donal.k.fellows@manchester.ac.uk>2012-03-11 17:03:00 (GMT)
committerdkf <donal.k.fellows@manchester.ac.uk>2012-03-11 17:03:00 (GMT)
commitc93c3a3b39929c9a7f1c816f4dc8a058f9eea85c (patch)
tree505d98c9c1a78785f5425cbf44b19004b4d49516 /doc/binary.n
parent014ce74e1d7d90d99e3b310e2e4a923f789802a2 (diff)
downloadtcl-c93c3a3b39929c9a7f1c816f4dc8a058f9eea85c.zip
tcl-c93c3a3b39929c9a7f1c816f4dc8a058f9eea85c.tar.gz
tcl-c93c3a3b39929c9a7f1c816f4dc8a058f9eea85c.tar.bz2
A number of small spelling and wording fixes in the docs.
Diffstat (limited to 'doc/binary.n')
-rw-r--r--doc/binary.n4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/binary.n b/doc/binary.n
index 8133829..68bf9cc 100644
--- a/doc/binary.n
+++ b/doc/binary.n
@@ -92,7 +92,7 @@ Instructs the decoder to throw an error if it encounters whitespace characters.
.
The \fBuuencode\fR binary encoding used to be common for transfer of data
between Unix systems and on USENET, but is less common these days, having been
-largely superceded by the \fBbase64\fR binary encoding.
+largely superseded by the \fBbase64\fR binary encoding.
.RS
.PP
During encoding, the following options are supported:
@@ -135,7 +135,7 @@ is a non-negative decimal integer or \fB*\fR, which normally indicates
that all of the items in the value are to be used. If the number of
arguments does not match the number of fields in the format string
that consume arguments, then an error is generated. The flag character
-is ignored for for \fBbinary format\fR.
+is ignored for \fBbinary format\fR.
.PP
Here is a small example to clarify the relation between the field
specifiers and the arguments: