In Bluetooth section:

- A little rewording
- Some punctuation fixes

en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml

@@ -1373,7 +1373,7 @@ c2e8bc80      0    250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3    6    OPEN</scree
         Bluetooth authentication requests. The default configuration file is
         <filename>/etc/bluetooth/hcsecd.conf</filename>. An example section for
         a cellular phone with the PIN code arbitrarily set to
-        <quote>1234</quote> is shown below.</para>
+        <quote>1234</quote> is shown below:</para>
 
       <programlisting>device {
         bdaddr  00:80:37:29:19:a4;
@@ -1391,7 +1391,8 @@ c2e8bc80      0    250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3    6    OPEN</scree
         accepted, and request the PIN code. Enter the same PIN code as you
         have in <filename>hcsecd.conf</filename>. Now your PC and the remote
         device are paired. Alternatively, you can initiate pairing on the remote
-        device. Below in the sample <command>hcsecd</command> output.</para>
+        device.  The following is a sample of the
+        <application>hcsecd</application> daemon output:</para>
 
 <programlisting>hcsecd[16484]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4
 hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', link key doesn't exist
@@ -1462,7 +1463,7 @@ Bluetooth Profile Descriptor List:
         make a note of some of the attributes. Some Bluetooth implementations do
         not support service browsing and may return an empty list. In this case
         it is possible to search for the specific service. The example below
-        shows how to search for the OBEX Object Push (OPUSH) service.</para>
+        shows how to search for the OBEX Object Push (OPUSH) service:</para>
 
       <screen>&prompt.user; <userinput>sdpcontrol -a 00:01:03:fc:6e:ec search OPUSH</userinput></screen>