summaryrefslogtreecommitdiffstats
path: root/doc/Panic.3
diff options
context:
space:
mode:
Diffstat (limited to 'doc/Panic.3')
-rw-r--r--doc/Panic.34
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/Panic.3 b/doc/Panic.3
index ba39ddf..f3f8043 100644
--- a/doc/Panic.3
+++ b/doc/Panic.3
@@ -53,13 +53,13 @@ In a freshly loaded Tcl library, \fBTcl_Panic\fR prints the formatted
error message to the standard error file of the process, and then
calls \fBabort\fR to terminate the process. \fBTcl_Panic\fR does not
return. On Windows, when a debugger is running, the formatted error
-message is sent to the debugger in stead. If the windows executable
+message is sent to the debugger instead. If the windows executable
does not have a stderr channel (e.g. \fBwish.exe\fR), then a
system dialog box is used to display the panic message.
.PP
If your application doesn't use \fBTcl_Main\fR or \fBTk_Main\fR
and you want to implicitly use the stderr channel of your
-application's C runtime (in stead of the stderr channel of the
+application's C runtime (instead of the stderr channel of the
C runtime used by Tcl), you can call \fBTcl_SetPanicProc\fR
with \fBTcl_ConsolePanic\fR as its argument. On platforms which
only have one C runtime (almost all platforms except Windows)