Examples: some more misc fixes

examples/nfc-list.1

@@ -5,7 +5,7 @@ nfc-list \- List NFC targets
 .B nfc-list
 .SH DESCRIPTION
 .B nfc-list
-is a utility for listing any available targets like ISO14443-A, FeliCa, Jewel
+is a utility for listing any available tags like ISO14443-A, FeliCa, Jewel
 or ISO14443-B (according to the device capabilities).
 It may detect several tags at once thanks to a mechanism called anti-collision
 but all types of tags don't support anti-collision and there is some physical

examples/nfc-mfclassic.1

@@ -24,6 +24,9 @@ and its ease-of-use. It's possible to read and write the complete content of a
 Mifare Classic 4KB tag within 1 second. It uses a binary Mifare Dump file (MFD)
 to store the keys and data for all sectors.
 
+Be cautious that some parts of a Mifare Classic memory are used for r/w access
+of the rest of the memory, so please read the tag documentation before experimenting too much!
+
 .SH OPTIONS
 .BR r " | " w
 Perform read from (

examples/nfc-mfultralight.1

@@ -8,13 +8,18 @@ nfc-mfultralight \- MIFARE Ultralight command line tool
 
 .SH DESCRIPTION
 .B nfc-mfultralight
-is a MIFARE Ultralight tool that allow to read or write
+is a MIFARE Ultralight tool that allows to read or write
+a tag data to/from a
 .IR DUMP
 file.
 
 MIFARE Ultralight tag is one of the most widely used RFID tags for ticketing application.
 It uses a binary Mifare Dump file (MFD) to store data for all sectors.
 
+Be cautious that some parts of a Ultralight memory can be written only once
+and some parts are used as lock bits, so please read the tag documentation
+before experimenting too much!
+
 .SH OPTIONS
 .BR r " | " w
 Perform read from (

examples/nfc-poll.1

@@ -5,11 +5,11 @@ nfc-poll \- Poll for one NFC target
 .B nfc-poll
 .SH DESCRIPTION
 .B nfc-poll
-is a utility for polling any available target using ISO14443-A, FeliCa, Jewel
+is a utility for polling any available target (tags but also NFCIP targets)
-and ISO14443-B modulations.
+using ISO14443-A, FeliCa, Jewel and ISO14443-B modulations.
 
 This tool relies on a hardware polling feature of the PN532, it will display
-available information retrived from the tag.
+available information retrieved from the tag.
 
 .SH BUGS
 Please report any bugs on the

examples/nfc-relay.1

@@ -5,7 +5,7 @@ nfc-relay \- Relay attack command line tool based on libnfc
 .B nfc-relay
 .SH DESCRIPTION
 .B nfc-relay
-is an utility that demonstrates an relay attack.
+is a utility that demonstrates a relay attack.
 
 This tool requires two NFC devices. One device (configured as target) will
 emulate an ISO/IEC 14443 type A tag, while the second device (configured as
@@ -14,6 +14,9 @@ device (initiator) and the tag emulator (target) can be placed close to the
 original reader. All communication is now relayed and shown in the screen on
 real-time.
 
+This tool has the same issues regarding timing as \fBnfc-emulate-uid\fP has,
+therefore we advise you to try it against e.g. an OmniKey CardMan 5321 reader.
+
 .SH BUGS
 Please report any bugs on the
 .B libnfc

examples/nfcip-initiator.1

@@ -5,11 +5,11 @@ nfcip-initiator \- Demonstration tool to send/received data as D.E.P. initiator
 .B nfcip-initiator
 .SH DESCRIPTION
 .B nfcip-initiator
-is a demonstration tool for puting NFC device in D.E.P. initiator mode.
+is a demonstration tool for putting NFC device in D.E.P. initiator mode.
 
 This example will attempt to select a passive D.E.P. target and exchange a simple "Hello" data with target.
 
-Note: this example is designed to work with a D.E.P. target driven by nfcip-target
+Note: this example is designed to work with a D.E.P. target driven by \fBnfcip-target\fP
 
 .SH BUGS
 Please report any bugs on the

examples/nfcip-target.1

@@ -5,11 +5,11 @@ nfcip-target \- Demonstration tool to send/received data as D.E.P. target
 .B nfcip-target
 .SH DESCRIPTION
 .B nfcip-target
-is a demonstration tool for puting NFC device in D.E.P. target mode.
+is a demonstration tool for putting NFC device in D.E.P. target mode.
 
 This example will listen for a D.E.P. initiator and exchange a simple "Hello" data with initiator.
 
-Note: this example is designed to work with a D.E.P. initiator driven by nfcip-initiator
+Note: this example is designed to work with a D.E.P. initiator driven by \fBnfcip-initiator\fP.
 
 .SH BUGS
 Please report any bugs on the

examples/pn53x-diagnose.1

@@ -6,7 +6,7 @@ pn53x-diagnose \- PN53x diagnose tool
 .SH DESCRIPTION
 .B pn53x-diagnose
 is a utility to diagnose PN531, PN532 and PN533 chips.
-It run communication, RAM and ROM tests.
+It runs communication, RAM and ROM tests.
 
 .SH BUGS
 Please report any bugs on the

examples/pn53x-sam.1

@@ -1,16 +1,19 @@
 .TH PN53X-SAM 1 "June 15, 2010"
 .SH NAME
-pn53x-sam \- PN53x SAM comunication demonstration tool
+pn53x-sam \- PN53x SAM communication demonstration tool
 .SH SYNOPSIS
 .B pn53x-sam
 .SH DESCRIPTION
 .B pn53x-sam
-is a utility attempts to test a simple connection with a SAM (Secure Access
+is a utility attempt to test a simple connection with a SAM (Secure Access
 Module) in several modes.
 
 To run this utility you must have a SAM (like the NXP's P5CN072 chip)
 successfully connected to your PN53x chip.
 
+Warning: the SAM inside the Touchatag is \fInot\fP hooked to the PN532
+but to the intermediate controller so \fBpn53x-sam\fP won't work with a Touchatag.
+
 .SH BUGS
 Please report any bugs on the
 .B libnfc