[rtems commit] stackchk.t task.t: Change can not to cannot for consistency

[Joel Sherrill]

Module:    rtems
Branch:    master
Commit:    30d1176618e7951f568dd889b16a5e87fd5fabb1
Changeset: http://git.rtems.org/rtems/commit/?id=30d1176618e7951f568dd889b16a5e87fd5fabb1

Author:    Joel Sherrill <joel.sherrill at oarcorp.com>
Date:      Tue Mar 11 15:08:54 2014 -0500

stackchk.t task.t: Change can not to cannot for consistency

---

 doc/user/stackchk.t |    2 +-
 doc/user/task.t     |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/user/stackchk.t b/doc/user/stackchk.t
index 53077c2..3097356 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:
 
diff --git a/doc/user/task.t b/doc/user/task.t
index b55d9b7..40759fc 100644
--- a/doc/user/task.t
+++ b/doc/user/task.t
@@ -318,7 +318,7 @@ variable's value each time a task switch occurs to or from the calling task.
 
 The value seen by other tasks, including those which have not added the
 variable to their set and are thus accessing the variable as a common
-location shared among tasks, can not be affected by a task once it has
+location shared among tasks, cannot be affected by a task once it has
 added a variable to its local set.  Changes made to the variable by
 other tasks will not affect the value seen by a task which has added the
 variable to its private set.