Minor comment

diff --git a/docs/howtos/HowToDebugVKernels/index.mdwn b/docs/howtos/HowToDebugVKernels/index.mdwn
index 4b5ac6c..75b566b 100644 (file)
--- a/docs/howtos/HowToDebugVKernels/index.mdwn
+++ b/docs/howtos/HowToDebugVKernels/index.mdwn
@@ -180,7 +180,7 @@ Let's see if this process is traced (if it is, the p->p_tracenode->kn_vp shall p
     $2 = (struct ktrace_node *) 0x0
     (gdb) 
 
-Oops. There is no trace to any vnode, whatsoever, for this process. The code will try to access p->p_tracenode and is bound to crash. This is the _zero virtual address_ we saw before. Now that we know the root of problem we write a [patch](http://gitweb.dragonflybsd.org/dragonfly.git/commit/a4a639859f6bc14f9f55142b4bd2289b2a56d7f2) and poke someone to review/commit it.
+Oops. There is no trace to any vnode, whatsoever, for this process. The code will try to access p->p_tracenode and is bound to crash. This is the _zero virtual address_ we saw before. It seems that the kernel tries to disable tracing of processes indiscriminately. Now that we know the root of problem we write a [patch](http://gitweb.dragonflybsd.org/dragonfly.git/commit/a4a639859f6bc14f9f55142b4bd2289b2a56d7f2) and poke someone to review/commit it.
 
 # Possible places of confusion