Attachment "docs_tcl_builtin.patch" to
ticket [1018486fff]
added by
mkolesn
2004-08-29 16:40:24.
Index: binary.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/binary.n,v
retrieving revision 1.19
diff -u -r1.19 binary.n
--- binary.n 15 Jun 2004 22:22:37 -0000 1.19
+++ binary.n 28 Aug 2004 17:39:48 -0000
@@ -22,7 +22,7 @@
.PP
This command provides facilities for manipulating binary data. The
first form, \fBbinary format\fR, creates a binary string from normal
-Tcl values. For example, given the values 16 and 22, on a 32 bit
+Tcl values. For example, given the values 16 and 22, on a 32-bit
architecture, it might produce an 8-byte binary string consisting of
two 4-byte integers, one for each of the numbers. The second form of
the command, \fBbinary scan\fR, does the opposite: it extracts data
@@ -700,7 +700,7 @@
.IP \fBx\fR 5
Moves the cursor forward \fIcount\fR bytes in \fIstring\fR. If
\fIcount\fR is \fB*\fR or is larger than the number of bytes after the
-current cursor cursor position, then the cursor is positioned after
+current cursor position, then the cursor is positioned after
the last byte in \fIstring\fR. If \fIcount\fR is omitted, then the
cursor is moved forward one byte. Note that this type does not
consume an argument. For example,
Index: catch.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/catch.n,v
retrieving revision 1.9
diff -u -r1.9 catch.n
--- catch.n 16 Mar 2004 22:19:43 -0000 1.9
+++ catch.n 28 Aug 2004 17:47:30 -0000
@@ -28,7 +28,7 @@
If \fIscript\fR raises an error, \fBcatch\fR will return a non-zero integer
value corresponding to the exceptional return code returned by evaluation
of \fIscript\fR. Tcl defines the normal return code from script
-evalation to be zero (0), or TCL_OK. Tcl also defines four exceptional
+evaluation to be zero (0), or TCL_OK. Tcl also defines four exceptional
return codes: 1 (TCL_ERROR), 2 (TCL_RETURN), 3 (TCL_BREAK),
and 4 (TCL_CONTINUE). Errors during evaluation of a script are indicated
by a return code of TCL_ERROR. The other exceptional return codes are
Index: clock.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/clock.n,v
retrieving revision 1.18
diff -u -r1.18 clock.n
--- clock.n 18 Aug 2004 19:58:58 -0000 1.18
+++ clock.n 28 Aug 2004 17:59:16 -0000
@@ -46,7 +46,7 @@
usage is obsolete, and \fBclock milliseconds\fR is to be
considered the preferred way of obtaining a count of milliseconds.
.sp
-It the \fI-option\fR argument is \fI-microseconds\fR, then the command
+If the \fI-option\fR argument is \fI-microseconds\fR, then the command
is synonymous with \fBclock microseconds\fR (see below). This
usage is obsolete, and \fBclock microseconds\fR is to be
considered the preferred way of obtaining a count of microseconds.
@@ -827,7 +827,7 @@
of a long month to a short month.
.PP
Daylight savings time correction is applied only when the relative time
-is specified in units of days or more, ie, days, weeks, fortnights, months or
+is specified in units of days or more, i.e., days, weeks, fortnights, months or
years. This means that when crossing the daylight savings time boundary,
different results will be given for \fBclock scan "1 day"\fR and
\fBclock scan "24 hours"\fR:
Index: dde.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/dde.n,v
retrieving revision 1.13
diff -u -r1.13 dde.n
--- dde.n 25 May 2004 21:06:41 -0000 1.13
+++ dde.n 28 Aug 2004 19:24:44 -0000
@@ -58,7 +58,7 @@
\fI-force\fR option is used to force registration of precisely the
given \fItopic\fR name.
.IP
-The \fI-handler\fR option specifies a tcl procedure that will be called to
+The \fI-handler\fR option specifies a Tcl procedure that will be called to
process calls to the dde server. If the package has been loaded into a
safe interpreter then a \fI-handler\fR procedure must be defined. The
procedure is called with all the arguments provided by the remote
Index: dict.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/dict.n,v
retrieving revision 1.4
diff -u -r1.4 dict.n
--- dict.n 27 May 2004 23:53:55 -0000 1.4
+++ dict.n 28 Aug 2004 20:15:48 -0000
@@ -131,7 +131,7 @@
the resulting dictionary value back to that variable. Non-existent
keys are treated as if they map to an empty list, and it is legal for
there to be no items to append to the list. It is an error for the
-value that the key maps to to not be representable as a list.
+value that the key maps to not be representable as a list.
.TP
\fBdict merge \fR?\fIdictionaryValue ...\fR?
Return a dictionary that contains the contents of each of the
Index: exec.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/exec.n,v
retrieving revision 1.10
diff -u -r1.10 exec.n
--- exec.n 2 Jul 2004 23:31:29 -0000 1.10
+++ exec.n 28 Aug 2004 18:46:50 -0000
@@ -12,7 +12,7 @@
.BS
'\" Note: do not modify the .SH NAME line immediately below!
.SH NAME
-exec \- Invoke subprocess(es)
+exec \- Invoke subprocesses
.SH SYNOPSIS
\fBexec \fR?\fIswitches\fR? \fIarg \fR?\fIarg ...\fR?
.BE
@@ -38,7 +38,7 @@
Marks the end of switches. The argument following this one will
be treated as the first \fIarg\fR even if it starts with a \fB\-\fR.
.PP
-If an \fIarg\fR (or pair of \fIarg\fR's) has one of the forms
+If an \fIarg\fR (or pair of \fIarg\fRs) has one of the forms
described below then it is used by \fBexec\fR to control the
flow of input and output among the subprocess(es).
Such arguments will not be passed to the subprocess(es). In forms
@@ -225,7 +225,7 @@
.br
2) TUI -- Textmode User Interface, any application that accesses the console
API for doing such things as cursor movement, setting text color, detecting
-key presses and mouse movement, etc... An example would be \fBtelnet.exe\fR
+key presses and mouse movement, etc. An example would be \fBtelnet.exe\fR
from Windows 2000. These types of applications are not common in a windows
environment, but do exist.
.RE
@@ -233,7 +233,7 @@
present, as is done when launching applications under wish. It is desirable
to have console applications hidden and detached. This is a designed-in
limitation as \fBexec\fR wants to communicate over pipes. The Expect
-extension addresses this issue when communication between a TUI application
+extension addresses this issue when communication between TUI applications
is desired.
.sp
.RE
@@ -262,8 +262,8 @@
The directories listed in the path.
.RE
.sp
-In order to execute the shell builtin commands like \fBdir\fR and \fBcopy\fR,
-the caller must prepend ``\fBcmd.exe /c\0\fR'' to the desired command.
+In order to execute the shell built-in commands like \fBdir\fR and \fBcopy\fR,
+the caller must prepend desired command with ``\fBcmd.exe /c\0\fR''.
.sp
.RE
.TP
@@ -289,8 +289,8 @@
The directories listed in the path.
.RE
.sp
-In order to execute the shell builtin commands like \fBdir\fR and \fBcopy\fR,
-the caller must prepend ``\fBcommand.com /c\0\fR'' to the desired command.
+In order to execute the shell built-in commands like \fBdir\fR and \fBcopy\fR,
+the caller must prepend desired command with ``\fBcommand.com /c\0\fR''.
.sp
Once a 16-bit DOS application has read standard input from a console and
then quit, all subsequently run 16-bit DOS applications will see the
Index: file.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/file.n,v
retrieving revision 1.35
diff -u -r1.35 file.n
--- file.n 2 Jun 2004 14:24:05 -0000 1.35
+++ file.n 28 Aug 2004 19:20:20 -0000
@@ -271,7 +271,7 @@
\fBfile normalize \fIname\fR
.
.RS
-Returns a unique normalised path representation for the file-system
+Returns a unique normalized path representation for the file-system
object (file, directory, link, etc), whose string value can be used as a
unique identifier for it. A normalized path is an absolute path which has
all '../', './' removed. Also it is one which is in the ``standard''
Index: format.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/format.n,v
retrieving revision 1.8
diff -u -r1.8 format.n
--- format.n 7 May 2004 23:29:18 -0000 1.8
+++ format.n 28 Aug 2004 17:45:32 -0000
@@ -132,7 +132,7 @@
This option is rarely useful.
.VS 8.4
If it is \fBl\fR it specifies that the numeric value should be (at
-least) a 64-bit value. If neither \fBh\fR or \fBl\fR are present,
+least) a 64-bit value. If neither \fBh\fR nor \fBl\fR are present,
numeric values are interpreted as being values of the width of the
native machine word, as described by \fBtcl_platform(wordSize)\fR.
.VE
Index: history.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/history.n,v
retrieving revision 1.2
diff -u -r1.2 history.n
--- history.n 14 Sep 1998 18:39:53 -0000 1.2
+++ history.n 28 Aug 2004 19:26:28 -0000
@@ -82,7 +82,7 @@
event number in command-line prompts.
.TP
\fBhistory redo \fR?\fIevent\fR?
-Re-executes the command indicated by \fIevent\fR and return its result.
+Re-executes the command indicated by \fIevent\fR and returns its result.
\fIEvent\fR defaults to \fB\-1\fR. This command results in history
revision: see below for details.
.SH "HISTORY REVISION"
Index: http.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/http.n,v
retrieving revision 1.20
diff -u -r1.20 http.n
--- http.n 25 May 2004 22:56:29 -0000 1.20
+++ http.n 29 Aug 2004 08:42:14 -0000
@@ -55,7 +55,7 @@
policy, so it can be used by untrusted applets to do URL fetching from
a restricted set of hosts. This package can be extended to support
additional HTTP transport protocols, such as HTTPS, by providing
-a custom \fBsocket\fR command, via \fBhttp::register\fR.
+a custom \fBsocket\fR command, via \fB::http::register\fR.
.PP
The \fB::http::geturl\fR procedure does a HTTP transaction.
Its \fIoptions \fR determine whether a GET, POST, or HEAD transaction
@@ -88,7 +88,7 @@
\fB\-accept\fP \fImimetypes\fP
The Accept header of the request. The default is */*, which means that
all types of documents are accepted. Otherwise you can supply a
-comma separated list of mime type patterns that you are
+comma-separated list of mime type patterns that you are
willing to receive. For example, "image/gif, image/jpeg, text/*".
.TP
\fB\-proxyhost\fP \fIhostname\fP
@@ -103,7 +103,7 @@
\fB::http::geturl\fR
to determine if a proxy is required for a given host. One argument, a
host name, is added to \fIcommand\fR when it is invoked. If a proxy
-is required, the callback should return a two element list containing
+is required, the callback should return a two-element list containing
the proxy server and proxy port. Otherwise the filter should return
an empty list. The default filter returns the values of the
\fB\-proxyhost\fR and \fB\-proxyport\fR settings if they are
@@ -137,13 +137,13 @@
.RS
.TP
\fB\-binary\fP \fIboolean\fP
-Specifies whether to force interpreting the url data as binary. Normally
+Specifies whether to force interpreting the URL data as binary. Normally
this is auto-detected (anything not beginning with a \fBtext\fR content
type or whose content encoding is \fBgzip\fR or \fBcompress\fR is
considered binary data).
.TP
\fB\-blocksize\fP \fIsize\fP
-The blocksize used when reading the URL.
+The block size used when reading the URL.
At most \fIsize\fR bytes are read at once. After each block, a call to the
\fB\-progress\fR callback is made (if that option is specified).
.TP
@@ -217,12 +217,12 @@
.TP
\fB\-query\fP \fIquery\fP
This flag causes \fB::http::geturl\fR to do a POST request that passes the
-\fIquery\fR to the server. The \fIquery\fR must be a x-url-encoding
+\fIquery\fR to the server. The \fIquery\fR must be an x-url-encoding
formatted query. The \fB::http::formatQuery\fR procedure can be used to
do the formatting.
.TP
\fB\-queryblocksize\fP \fIsize\fP
-The blocksize used when posting query data to the URL.
+The block size used when posting query data to the URL.
At most
\fIsize\fR
bytes are written at once. After each block, a call to the
@@ -231,7 +231,7 @@
.TP
\fB\-querychannel\fP \fIchannelID\fP
This flag causes \fB::http::geturl\fR to do a POST request that passes the
-data contained in \fIchannelID\fR to the server. The data contained in \fIchannelID\fR must be a x-url-encoding
+data contained in \fIchannelID\fR to the server. The data contained in \fIchannelID\fR must be an x-url-encoding
formatted query unless the \fB\-type\fP option below is used.
If a Content-Length header is not specified via the \fB\-headers\fR options,
\fB::http::geturl\fR attempts to determine the size of the post data
@@ -328,18 +328,18 @@
package require http
package require tls
-http::register https 443 ::tls::socket
+::http::register https 443 ::tls::socket
-set token [http::geturl https://my.secure.site/]
+set token [::http::geturl https://my.secure.site/]
.CE
.RE
.TP
\fB::http::unregister\fP \fIproto\fP
This procedure unregisters a protocol handler that was previously
-registered via \fBhttp::register\fR.
+registered via \fB::http::register\fR.
.SH "ERRORS"
-The \fBhttp::geturl\fP procedure will raise errors in the following cases:
+The \fB::http::geturl\fP procedure will raise errors in the following cases:
invalid command line options,
an invalid URL,
a URL on a non-existent host,
@@ -371,17 +371,17 @@
callback does.
.PP
In any case, you must still call
-\fBhttp::cleanup\fP to delete the state array when you're done.
+\fB::http::cleanup\fP to delete the state array when you're done.
.PP
There are other possible results of the HTTP transaction
-determined by examining the status from \fBhttp::status\fP.
+determined by examining the status from \fB::http::status\fP.
These are described below.
.TP
ok
If the HTTP transaction completes entirely, then status will be \fBok\fP.
-However, you should still check the \fBhttp::code\fP value to get
-the HTTP status. The \fBhttp::ncode\fP procedure provides just
-the numeric error (e.g., 200, 404 or 500) while the \fBhttp::code\fP
+However, you should still check the \fB::http::code\fP value to get
+the HTTP status. The \fB::http::ncode\fP procedure provides just
+the numeric error (e.g., 200, 404 or 500) while the \fB::http::code\fP
procedure returns a value like "HTTP 404 File not found".
.TP
eof
@@ -392,11 +392,11 @@
The error message will also be stored in the \fBerror\fP status
array element, accessible via \fB::http::error\fP.
.PP
-Another error possibility is that \fBhttp::geturl\fP is unable to
+Another error possibility is that \fB::http::geturl\fP is unable to
write all the post query data to the server before the server
responds and closes the socket.
The error message is saved in the \fBposterror\fP status array
-element and then \fBhttp::geturl\fP attempts to complete the
+element and then \fB::http::geturl\fP attempts to complete the
transaction.
If it can read the server's response
it will end up with an \fBok\fP status, otherwise it will have
@@ -409,9 +409,9 @@
.CS
upvar #0 $token state
.CE
-Once the data associated with the url is no longer needed, the state
+Once the data associated with the URL is no longer needed, the state
array should be unset to free up storage.
-The \fBhttp::cleanup\fP procedure is provided for that purpose.
+The \fB::http::cleanup\fP procedure is provided for that purpose.
The following elements of
the array are supported:
.RS
@@ -503,7 +503,7 @@
set token [geturl $url -channel $out -progress ::http::Progress \\
-blocksize $chunk]
close $out
- # This ends the line started by http::Progress
+ # This ends the line started by ::http::Progress
puts stderr ""
upvar #0 $token state
set max 0
Index: info.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/info.n,v
retrieving revision 1.10
diff -u -r1.10 info.n
--- info.n 28 May 2004 10:49:09 -0000 1.10
+++ info.n 28 Aug 2004 19:30:58 -0000
@@ -48,7 +48,7 @@
Matching is determined using the same rules as for \fBstring match\fR.
\fIpattern\fR can be a qualified name like \fBFoo::print*\fR.
That is, it may specify a particular namespace
-using a sequence of namespace names separated by \fB::\fRs,
+using a sequence of namespace names separated by \fB::\fR ,
and may have pattern matching special characters
at the end to specify a set of commands in that namespace.
If \fIpattern\fR is a qualified name,
@@ -57,7 +57,7 @@
.TP
\fBinfo complete \fIcommand\fR
Returns 1 if \fIcommand\fR is a complete Tcl command in the sense of
-having no unclosed quotes, braces, brackets or array element names,
+having no unclosed quotes, braces, brackets or array element names.
If the command doesn't appear to be complete then 0 is returned.
This command is typically used in line-oriented input environments
to allow users to type in commands that span multiple lines; if the
@@ -193,7 +193,7 @@
\fBstring match\fR.
\fIpattern\fR can be a qualified name like \fBFoo::option*\fR.
That is, it may specify a particular namespace
-using a sequence of namespace names separated by \fB::\fRs,
+using a sequence of namespace names separated by \fB::\fR ,
and may have pattern matching special characters
at the end to specify a set of variables in that namespace.
If \fIpattern\fR is a qualified name,
Index: lindex.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/lindex.n,v
retrieving revision 1.7
diff -u -r1.7 lindex.n
--- lindex.n 14 Nov 2001 23:15:33 -0000 1.7
+++ lindex.n 28 Aug 2004 17:37:10 -0000
@@ -20,7 +20,7 @@
.SH DESCRIPTION
.PP
.VS 8.4
-The \fBlindex\fP command accepts a parameter, \fIlist\fP, which
+The \fBlindex\fP command accepts a parameter \fIlist\fP, which
it treats as a Tcl list. It also accepts zero or more \fIindices\fP into
the list. The indices may be presented either consecutively on the
command line, or grouped in a
Index: linsert.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/linsert.n,v
retrieving revision 1.8
diff -u -r1.8 linsert.n
--- linsert.n 16 Apr 2004 22:20:58 -0000 1.8
+++ linsert.n 28 Aug 2004 20:03:54 -0000
@@ -21,7 +21,7 @@
.SH DESCRIPTION
.PP
This command produces a new list from \fIlist\fR by inserting all of the
-\fIelement\fR arguments just before the \fIindex\fRth element of
+\fIelement\fR arguments just before the \fIindex\fR'th element of
\fIlist\fR. Each \fIelement\fR argument will become a separate element of
the new list. If \fIindex\fR is less than or equal to zero, then the new
elements are inserted at the beginning of the list. If \fIindex\fR has the
Index: lsearch.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/lsearch.n,v
retrieving revision 1.19
diff -u -r1.19 lsearch.n
--- lsearch.n 7 Jun 2004 21:41:27 -0000 1.19
+++ lsearch.n 28 Aug 2004 20:13:14 -0000
@@ -83,7 +83,7 @@
.TP
\fB\-ascii\fR
The list elements are to be examined as Unicode strings (the name is
-for backward-compatability reasons.)
+for backward-compatibility reasons.)
.TP
\fB\-dictionary\fR
The list elements are to be compared using dictionary-style
Index: lsort.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/lsort.n,v
retrieving revision 1.15
diff -u -r1.15 lsort.n
--- lsort.n 18 May 2004 20:47:38 -0000 1.15
+++ lsort.n 28 Aug 2004 20:14:28 -0000
@@ -33,7 +33,7 @@
.TP 20
\fB\-ascii\fR
Use string comparison with Unicode code-point collation order (the
-name is for backward-compatability reasons.) This is the default.
+name is for backward-compatibility reasons.) This is the default.
.TP 20
\fB\-dictionary\fR
Use dictionary-style comparison. This is the same as \fB\-ascii\fR
Index: msgcat.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/msgcat.n,v
retrieving revision 1.19
diff -u -r1.19 msgcat.n
--- msgcat.n 30 May 2004 14:56:32 -0000 1.19
+++ msgcat.n 28 Aug 2004 19:57:24 -0000
@@ -90,9 +90,9 @@
the user, based on the user's language specification.
The list is ordered from most specific to least
preference. The list is derived from the current
-locale set in msgcat by \fBmsgcat::mclocale\fR, and
+locale set in msgcat by \fB::msgcat::mclocale\fR, and
cannot be set independently. For example, if the
-current locale is en_US_funky, then \fBmsgcat::mcpreferences\fR
+current locale is en_US_funky, then \fB::msgcat::mcpreferences\fR
.VS 1.4
returns \fB{en_US_funky en_US en {}}\fR.
.VE
@@ -121,8 +121,8 @@
namespace.
\fIsrc-trans-list\fR must have an even number of elements and is in
the form {\fIsrc-string translate-string\fR ?\fIsrc-string
-translate-string ...\fR?} \fBmsgcat::mcmset\fR can be significantly
-faster than multiple invocations of \fBmsgcat::mcset\fR. The function
+translate-string ...\fR?} \fB::msgcat::mcmset\fR can be significantly
+faster than multiple invocations of \fB::msgcat::mcset\fR. The function
returns the number of translations set.
.TP
\fB::msgcat::mcunknown \fIlocale src-string\fR
@@ -155,7 +155,7 @@
language[_country][.codeset][@modifier]
.CE
to extract its parts. The initial locale is then set by calling
-\fBmsgcat::mclocale\fR with the argument
+\fB::msgcat::mclocale\fR with the argument
.CS
language[_country][_modifier]
.CE
Index: namespace.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/namespace.n,v
retrieving revision 1.14
diff -u -r1.14 namespace.n
--- namespace.n 21 May 2004 22:57:39 -0000 1.14
+++ namespace.n 28 Aug 2004 20:56:48 -0000
@@ -24,8 +24,8 @@
separate contexts for commands and variables.
See the section \fBWHAT IS A NAMESPACE?\fR below
for a brief overview of namespaces.
-The legal \fIoption\fR's are listed below.
-Note that you can abbreviate the \fIoption\fR's.
+The legal \fIoption\fRs are listed below.
+Note that you can abbreviate the \fIoption\fRs.
.TP
\fBnamespace children \fR?\fInamespace\fR? ?\fIpattern\fR?
Returns a list of all child namespaces that belong to the
@@ -33,7 +33,7 @@
If \fInamespace\fR is not specified,
then the children are returned for the current namespace.
This command returns fully-qualified names,
-which start with \fB::\fR.
+which start with \fB::\fR .
If the optional \fIpattern\fR is given,
then this command returns only the names that match the glob-style pattern.
The actual pattern used is determined as follows:
@@ -136,7 +136,7 @@
Removes previously imported commands from a namespace.
Each \fIpattern\fR is a simple or qualified name such as
\fBx\fR, \fBfoo::x\fR or \fBa::b::p*\fR.
-Qualified names contain \fB::\fRs and qualify a name
+Qualified names contain \fB::\fR and qualify a name
with the name of one or more namespaces.
Each \fIqualified pattern\fR is qualified with the name of an
exporting namespace
@@ -218,7 +218,7 @@
.TP
\fBnamespace qualifiers\fR \fIstring\fR
Returns any leading namespace qualifiers for \fIstring\fR.
-Qualifiers are namespace names separated by \fB::\fRs.
+Qualifiers are namespace names separated by \fB::\fR .
For the \fIstring\fR \fB::foo::bar::x\fR,
this command returns \fB::foo::bar\fR,
and for \fB::\fR it returns an empty string.
@@ -229,7 +229,7 @@
.TP
\fBnamespace tail\fR \fIstring\fR
Returns the simple name at the end of a qualified string.
-Qualifiers are namespace names separated by \fB::\fRs.
+Qualifiers are namespace names separated by \fB::\fR .
For the \fIstring\fR \fB::foo::bar::x\fR,
this command returns \fBx\fR,
and for \fB::\fR it returns an empty string.
@@ -331,7 +331,7 @@
As an example, the name \fB::safe::interp::create\fR
refers to the command \fBcreate\fR in the namespace \fBinterp\fR
that is a child of namespace \fB::safe\fR,
-which in turn is a child of the global namespace \fB::\fR.
+which in turn is a child of the global namespace \fB::\fR .
.PP
If you want to access commands and variables from another namespace,
you must use some extra syntax.
@@ -371,8 +371,8 @@
Namespaces have nonempty names except for the global namespace.
\fB::\fR is disallowed in simple command, variable, and namespace names
except as a namespace separator.
-Extra \fB:\fRs in a qualified name are ignored;
-that is, two or more \fB:\fRs are treated as a namespace separator.
+Extra colons in a qualified name are ignored;
+that is, two or more colons are treated as a namespace separator.
A trailing \fB::\fR in a qualified variable or command name
refers to the variable or command named {}.
However, a trailing \fB::\fR in a qualified namespace name is ignored.
@@ -443,7 +443,7 @@
This means, for example,
that a \fBnamespace eval\fR command that creates a new namespace
always creates a child of the current namespace
-unless the new namespace name begins with a \fB::\fR.
+unless the new namespace name begins with a \fB::\fR .
.PP
Tcl has no access control to limit what variables, commands,
or namespaces you can reference.
@@ -513,7 +513,7 @@
\fBnamespace import \-force Blt::graph Blt::table\fR
.CE
If for some reason, you want to stop using the imported commands,
-you can remove them with an \fBnamespace forget\fR command, like this:
+you can remove them with a \fBnamespace forget\fR command, like this:
.CS
\fBnamespace forget Blt::*\fR
.CE
@@ -669,7 +669,7 @@
name in the namespace linked to the ensemble. If this option is
empty, the subcommands of the namespace will either be the keys of the
dictionary listed in the \fB\-map\fR option or the exported commands
-of the linked namespace at the time of the invokation of the ensemble
+of the linked namespace at the time of the invocation of the ensemble
command.
.TP
\fB\-unknown\fR
@@ -723,7 +723,7 @@
command attempts to look up the original subcommand again and, if it
is not found this time, an error will be generated just as if the
\fB\-unknown\fR handler was not there (i.e. for any particular
-invokation of an ensemble, its unknown handler will be called at most
+invocation of an ensemble, its unknown handler will be called at most
once.) This makes it easy for the unknown handler to update the
ensemble or its backing namespace so as to provide an implementation
of the desired subcommand and reparse.
Index: pid.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/pid.n,v
retrieving revision 1.4
diff -u -r1.4 pid.n
--- pid.n 28 May 2004 12:40:29 -0000 1.4
+++ pid.n 28 Aug 2004 19:23:16 -0000
@@ -12,7 +12,7 @@
.BS
'\" Note: do not modify the .SH NAME line immediately below!
.SH NAME
-pid \- Retrieve process id(s)
+pid \- Retrieve process ids
.SH SYNOPSIS
\fBpid \fR?\fIfileId\fR?
.BE
Index: registry.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/registry.n,v
retrieving revision 1.10
diff -u -r1.10 registry.n
--- registry.n 25 May 2004 15:30:19 -0000 1.10
+++ registry.n 28 Aug 2004 19:25:10 -0000
@@ -60,7 +60,7 @@
milliseconds, to wait for applications to respond to the broadcast message.
It defaults to 3000. The following example demonstrates how to add a path
to the global Environment and notify applications of the change without
-reguiring a logoff/logon step (assumes admin privileges):
+requiring a logoff/logon step (assumes admin privileges):
.CS
set regPath {HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment}
set curPath [registry get $regPath "Path"]
Index: socket.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/socket.n,v
retrieving revision 1.10
diff -u -r1.10 socket.n
--- socket.n 16 Apr 2004 12:58:52 -0000 1.10
+++ socket.n 28 Aug 2004 20:57:54 -0000
@@ -118,7 +118,7 @@
.PP
If \fIport\fR is specified as zero, the operating system will allocate
an unused port for use as a server socket. The port number actually
-allocated my be retrieved from the created server socket using the
+allocated may be retrieved from the created server socket using the
\fBfconfigure\fR command to retrieve the \fB\-sockname\fR option as
described below.
Index: trace.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/trace.n,v
retrieving revision 1.16
diff -u -r1.16 trace.n
--- trace.n 28 May 2004 00:05:02 -0000 1.16
+++ trace.n 28 Aug 2004 21:00:16 -0000
@@ -90,16 +90,16 @@
just after the actual execution takes place.
.TP
\fBenterstep\fR
-Invoke \fIcommand\fR for every tcl command which is executed
+Invoke \fIcommand\fR for every Tcl command which is executed
inside the procedure \fIname\fR, just before the actual execution
takes place. For example if we have 'proc foo {} { puts "hello" }',
-then a \fIenterstep\fR trace would be
+then an \fIenterstep\fR trace would be
invoked just before \fIputs "hello"\fR is executed.
-Setting a \fIenterstep\fR trace on a \fIcommand\fR
+Setting an \fIenterstep\fR trace on a \fIcommand\fR
will not result in an error and is simply ignored.
.TP
\fBleavestep\fR
-Invoke \fIcommand\fR for every tcl command which is executed
+Invoke \fIcommand\fR for every Tcl command which is executed
inside the procedure \fIname\fR, just after the actual execution
takes place.
Setting a \fIleavestep\fR trace on a \fIcommand\fR
