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 d7a639dd88..875b4d6568 100644
--- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
@@ -1679,13 +1679,9 @@ Bluetooth Profile Descriptor List:
into the phone's directory.
&prompt.user; obexapp -a 00:80:37:29:19:a4 -C IrMC
-obex> get
-get: remote file> telecom/devinfo.txt
-get: local file> devinfo-t39.txt
+obex> get telecom/devinfo.txt devinfo-t39.txt
Success, response: OK, Success (0x20)
-obex> put
-put: local file> new.vcf
-put: remote file> new.vcf
+obex> put new.vcf
Success, response: OK, Success (0x20)
obex> di
Success, response: OK, Success (0x20)
@@ -1745,9 +1741,9 @@ 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
- .
+ Yes, you can. Use the third-party package
+ hcidump, which is available as
+ comms/hcidump port.
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