kern/99632: [typo] sys/kern/kern_thread.c

[Cheng-Lung Sung]

>Number:         99632
>Category:       kern
>Synopsis:       [typo] sys/kern/kern_thread.c
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 30 05:50:14 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Cheng-Lung Sung
>Release:        FreeBSD 6.1-STABLE i386
>Organization:
>Environment:
System: FreeBSD going04.iis.sinica.edu.tw 6.1-STABLE FreeBSD 6.1-STABLE #20: Tue Jun 6 10:27:46 CST 2006 root at going04.iis.sinica.edu.tw:/usr/obj/usr/src/sys/GOING04 i386


>Description:
	accellerated shoule be accelerated
>How-To-Repeat:
>Fix:


--- sys/kern/kern_thread.c.orig	Fri Apr  7 10:40:16 2006
+++ sys/kern/kern_thread.c	Fri Jun 30 13:42:15 2006
@@ -698,7 +698,7 @@
  * There are no threads in user mode. Threads in the kernel must be
  * allowed to continue until they get to the user boundary. They may even
  * copy out their return values and data before suspending. They may however be
- * accellerated in reaching the user boundary as we will wake up
+ * accelerated in reaching the user boundary as we will wake up
  * any sleeping threads that are interruptable. (PCATCH).
  */
 int

>Release-Note:
>Audit-Trail:
>Unformatted: