diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
index ec5a4ad948..101ec78040 100644
--- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
@@ -1121,7 +1121,7 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
&man.ng.ubt.4; drivers. The 3Com Bluetooth PC Card 3CRWB60-A is
supported by the &man.ng.bt3c.4; driver. Serial and UART based
Bluetooth devices are supported via &man.sio.4;, &man.ng.h4.4;
- and &man.hcseriald.8;. This chapter describes the use of the USB
+ and &man.hcseriald.8;. This section describes the use of the USB
Bluetooth dongle. Bluetooth support is available in &os; 5.0 and newer
systems.
@@ -1130,18 +1130,18 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
Plugging in the Device
By default Bluetooth device drivers are available as kernel modules.
Before attaching a device, you will need to load the driver into the
- kernel.
+ kernel:
&prompt.root; kldload ng_ubt
If the Bluetooth device is present in the system during system
startup, load the module from
- /boot/loader.conf.
+ /boot/loader.conf:
ng_ubt_load="YES"
Plug in your USB dongle. The output similar to the following will
- appear on the console (or in syslog).
+ appear on the console (or in syslog):
ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
@@ -1190,7 +1190,7 @@ Number of SCO packets: 8
the L2CAP node (upstream). All HCI operations must be performed
on the HCI node and not on the device driver node. Default name
for the HCI node is devicehci
.
- For more details refer to the &man.ng.hci.4; man page.
+ For more details refer to the &man.ng.hci.4; manual page.
One of the most common tasks is discovery of Bluetooth devices in
RF proximity. This operation is called inquiry.
@@ -1219,7 +1219,7 @@ Inquiry complete. Status: No error [00]
The /etc/bluetooth/hosts file contains information
regarding the known Bluetooth hosts. The following example shows how
to obtain human readable name that was assigned to the remote
- device.
+ device:
&prompt.user; hccontrol -n ubt0hci remote_name_request 00:80:37:29:19:a4
BD_ADDR: 00:80:37:29:19:a4
@@ -1233,7 +1233,7 @@ Name: Pav's T39
Bluetooth units involved), or a point-to-multipoint connection. In the
point-to-multipoint connection the connection is shared among several
Bluetooth devices. The following example shows how to obtain the list
- of active baseband connections for the local device.
+ of active baseband connections for the local device:
&prompt.user; hccontrol -n ubt0hci read_connection_list
Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State
@@ -1278,11 +1278,11 @@ Reason: Connection terminated by local host [0x16]
connected to the Bluetooth HCI node (downstream) and Bluetooth sockets
nodes (upstream). Default name for the L2CAP node is
devicel2cap
. For more details refer to the
- &man.ng.l2cap.4; man page.
+ &man.ng.l2cap.4; manual page.
A useful command is &man.l2ping.8;, which can be used to ping
other devices. Some Bluetooth implementations might not return all of
- the data sent to them, so 0 bytes in the following
+ the data sent to them, so 0 bytes in the following
example is normal.
&prompt.root; l2ping -a 00:80:37:29:19:a4
@@ -1294,7 +1294,7 @@ Reason: Connection terminated by local host [0x16]
The &man.l2control.8; utility is used to perform various operations
on L2CAP nodes. This example shows how to obtain the list of logical
connections (channels) and the list of baseband connections for the
- local device.
+ local device:
&prompt.user; l2control -a 00:02:72:00:d4:1a read_channel_list
L2CAP channels:
@@ -1467,7 +1467,7 @@ Bluetooth Profile Descriptor List:
&prompt.user; sdpcontrol -a 00:01:03:fc:6e:ec search OPUSH
Offering services on &os; to Bluetooth clients is done with the
- &man.sdpd.8; server.
+ &man.sdpd.8; server:
&prompt.root; sdpd
The local server application that wants to provide Bluetooth
@@ -1477,7 +1477,7 @@ Bluetooth Profile Descriptor List:
SDP daemon.
The list of services registered with the local SDP server can be
- obtained by issuing SDP browse query via local control channel.
+ obtained by issuing SDP browse query via local control channel:
&prompt.root; sdpcontrol -l browse
@@ -1607,7 +1607,7 @@ Success, response: OK, Success (0x20)
&prompt.root; rfcomm_sppd -a 00:07:E0:00:0B:CA -t /dev/ttyp6
rfcomm_sppd[94692]: Starting on /dev/ttyp6...
- Once connected, the pseudo tty can be used as serial port.
+ Once connected, the pseudo tty can be used as serial port:
&prompt.root; cu -l ttyp6
@@ -1625,7 +1625,7 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...
performed when a new connection is being established, so it is not
possible to ask the remote device if it does support role switching.
There is a HCI option to disable role switching on the local
- side.
+ side:
&prompt.root; hccontrol -n ubt0hci write_node_role_switch 0
@@ -1635,7 +1635,7 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...
Something is going wrong, can I see what exactly is happening?
Yes, you can. Use the hcidump-1.5
third-party package that can be downloaded from
- here.
+ .
The hcidump utility is similar to
&man.tcpdump.1;. It can be used to display the content of the Bluetooth
packets on the terminal and to dump the Bluetooth packets to a