summaryrefslogtreecommitdiffstats
path: root/doc/user/stackchk.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@oarcorp.com>2014-03-11 15:08:54 -0500
committerJoel Sherrill <joel.sherrill@oarcorp.com>2014-03-11 16:27:57 -0500
commit30d1176618e7951f568dd889b16a5e87fd5fabb1 (patch)
treedd7bc18403c925bd2e014df8a04469d55b9eff93 /doc/user/stackchk.t
parentcpright.texi: Update to 2014. (diff)
downloadrtems-30d1176618e7951f568dd889b16a5e87fd5fabb1.tar.bz2
stackchk.t task.t: Change can not to cannot for consistency
Diffstat (limited to '')
-rw-r--r--doc/user/stackchk.t2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/stackchk.t b/doc/user/stackchk.t
index 53077c2df3..30973567e1 100644
--- a/doc/user/stackchk.t
+++ b/doc/user/stackchk.t
@@ -130,7 +130,7 @@ This is not actually a task, it is the interrupt stack.
When the stack bounds checker determines that a stack overflow has occurred,
it will attempt to print a message using @code{printk} identifying the
task and then shut the system down. If the stack overflow has caused
-corruption, then it is possible that the message can not be printed.
+corruption, then it is possible that the message cannot be printed.
The following is an example of the output generated: