Minor language tweaks.

Discussed with:	Hiten Pandya <hiten@unixdaemons.com>

en_US.ISO8859-1/articles/smp/article.sgml

@@ -63,7 +63,7 @@
       The kernel is basically one rather large and complex program. To
       make the kernel multithreaded we use some of the same tools used
       to make other programs multithreaded.  These include mutexes,
-      reader/writer locks, semaphores, and condition variables.  For
+      shared/exclusive locks, semaphores, and condition variables.  For
       definitions of many of the terms, please see
       <xref linkend="defs">.</para>
   </sect1>
@@ -579,8 +579,8 @@
 	this condition variable must only be waited on if the caller is
 	holding no other locks, or a lock order violation may be
 	possible.  The busy count, in effect, acts as a form of
-	reader/writer lock over access to the framework: the difference
-	is that, unlike with an sxlock, consumers waiting for the list
+	shared/exclusive lock over access to the framework: the difference
+	is that, unlike with an sx lock, consumers waiting for the list
 	to become unbusy may be starved, rather than permitting lock
 	order problems with regards to the busy count and other locks
 	that may be held on entry to (or inside) the MAC Framework.</para>
@@ -708,11 +708,10 @@
 	kernel statistics and configuration parameters, the sysctl
 	mechanism must become aware of appropriate locking semantics
 	for those variables.  Currently, sysctl makes use of a
-	single global <varname>sxlock</varname> to serialize use
-	of sysctl(); however, it is assumed to operate under Giant
-	and other protections are not provided.  The remainder of
-	this section speculates on locking and semantic changes
-	to sysctl.</para>
+	single global sx lock to serialize use of sysctl(); however, it
+	is assumed to operate under Giant and other protections are not
+	provided.  The remainder of this section speculates on locking
+	and semantic changes to sysctl.</para>
 
       <para>- Need to change the order of operations for sysctl's that
 	update values from read old, copyin and copyout, write new to

en_US.ISO8859-1/books/arch-handbook/smp/chapter.sgml

@@ -63,7 +63,7 @@
       The kernel is basically one rather large and complex program. To
       make the kernel multithreaded we use some of the same tools used
       to make other programs multithreaded.  These include mutexes,
-      reader/writer locks, semaphores, and condition variables.  For
+      shared/exclusive locks, semaphores, and condition variables.  For
       definitions of many of the terms, please see
       <xref linkend="defs">.</para>
   </sect1>
@@ -579,8 +579,8 @@
 	this condition variable must only be waited on if the caller is
 	holding no other locks, or a lock order violation may be
 	possible.  The busy count, in effect, acts as a form of
-	reader/writer lock over access to the framework: the difference
-	is that, unlike with an sxlock, consumers waiting for the list
+	shared/exclusive lock over access to the framework: the difference
+	is that, unlike with an sx lock, consumers waiting for the list
 	to become unbusy may be starved, rather than permitting lock
 	order problems with regards to the busy count and other locks
 	that may be held on entry to (or inside) the MAC Framework.</para>
@@ -708,11 +708,10 @@
 	kernel statistics and configuration parameters, the sysctl
 	mechanism must become aware of appropriate locking semantics
 	for those variables.  Currently, sysctl makes use of a
-	single global <varname>sxlock</varname> to serialize use
-	of sysctl(); however, it is assumed to operate under Giant
-	and other protections are not provided.  The remainder of
-	this section speculates on locking and semantic changes
-	to sysctl.</para>
+	single global sx lock to serialize use of sysctl(); however, it
+	is assumed to operate under Giant and other protections are not
+	provided.  The remainder of this section speculates on locking
+	and semantic changes to sysctl.</para>
 
       <para>- Need to change the order of operations for sysctl's that
 	update values from read old, copyin and copyout, write new to