[src/trunk]: src/sys/sys Spell LK_CANRECURSE correctly in the comment.

[uwe <uwe%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/5207546acf64
branches:  trunk
changeset: 586800:5207546acf64
user:      uwe <uwe%NetBSD.org@localhost>
date:      Mon Jan 02 21:53:30 2006 +0000

description:
Spell LK_CANRECURSE correctly in the comment.

diffstat:

 sys/sys/lock.h |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (18 lines):

diff -r de466a055845 -r 5207546acf64 sys/sys/lock.h
--- a/sys/sys/lock.h    Mon Jan 02 21:49:44 2006 +0000
+++ b/sys/sys/lock.h    Mon Jan 02 21:53:30 2006 +0000
@@ -1,4 +1,4 @@
-/*     $NetBSD: lock.h,v 1.62 2005/12/27 04:06:46 chs Exp $    */
+/*     $NetBSD: lock.h,v 1.63 2006/01/02 21:53:30 uwe Exp $    */
 
 /*-
  * Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
@@ -193,7 +193,7 @@
  *     lock. Only one exclusive lock may exist at a time, except that
  *     a process holding an exclusive lock may get additional exclusive
  *     locks if it explicitly sets the LK_CANRECURSE flag in the lock
- *     request, or if the LK_CANRECUSE flag was set when the lock was
+ *     request, or if the LK_CANRECURSE flag was set when the lock was
  *     initialized.
  *   LK_UPGRADE - the process must hold a shared lock that it wants to
  *     have upgraded to an exclusive lock. Other processes may get