From ca2e6faeaae3e6a777b4d56cdf0bb2e09f449b0f Mon Sep 17 00:00:00 2001 From: griffin Date: Sun, 26 May 2024 19:21:49 +0000 Subject: Fix spelling errors. --- doc/zipfs.n | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/zipfs.n b/doc/zipfs.n index 60b98c5..9ac283d 100644 --- a/doc/zipfs.n +++ b/doc/zipfs.n @@ -57,7 +57,7 @@ This takes the name of a file, \fIfilename\fR, and produces where it would be mapped into a zipfs mount as its result. If specified, \fImountpoint\fR says within which mount the mapping will be done; if omitted, the main root of the zipfs system is used. The \fIinZipfs\fR argument is a an optional boolean -which controls whether to fully canonicalise the name; it defaults to true. +which controls whether to fully canonicalize the name; it defaults to true. .\" METHOD: exists .TP \fBzipfs exists\fI filename\fR @@ -204,12 +204,12 @@ that \fBmain.tcl\fR after mounting the ZIP archive, and will \fBexit\fR once that script has been executed. .PP \fBNote:\fR \fBtclsh\fR and \fBwish\fR can be built using either -dynamic binding or static binding of the core implemenation +dynamic binding or static binding of the core implementation libraries. With a dynamic binding, the base application Tcl_Library contents are attached to the \fBlibtcl\fR and \fBlibtk\fR shared library, respectively. With a static binding, the Tcl_Library contents, etc., are attached to the application, \fBtclsh\fR or -\fBwish\fR. When using \fBmkimg\fR with a staticly built tclsh, it is +\fBwish\fR. When using \fBmkimg\fR with a statically built tclsh, it is the user's responsibility to preserve the attached archive by first extracting it to a temporary location, and then add whatever additional files desired, before creating and attaching the new -- cgit v0.12