From a2b022609f494d5658a9711e5ccfbb932ec498f7 Mon Sep 17 00:00:00 2001 From: Ludovic Rousseau Date: Sun, 13 May 2012 13:10:15 +0000 Subject: [PATCH] Fix some spelling mistakes Closes Issue #196 --- examples/nfc-emulate-tag.c | 2 +- examples/nfc-emulate-uid.1 | 2 +- libnfc/chips/pn53x-internal.h | 10 +++++----- libnfc/drivers/acr122_usb.c | 2 +- utils/nfc-emulate-forum-tag4.c | 2 +- utils/nfc-mfultralight.1 | 2 +- utils/nfc-read-forum-tag3.c | 2 +- utils/nfc-relay-picc.1 | 4 ++-- 8 files changed, 13 insertions(+), 13 deletions(-) diff --git a/examples/nfc-emulate-tag.c b/examples/nfc-emulate-tag.c index 2019d07..29d46a2 100644 --- a/examples/nfc-emulate-tag.c +++ b/examples/nfc-emulate-tag.c @@ -108,7 +108,7 @@ target_io( nfc_target *pnt, const uint8_t *pbtInput, const size_t szInput, uint8 case 0xe0: // RATS (ISO14443-4) // Send ATS *pszOutput = pnt->nti.nai.szAtsLen + 1; - pbtOutput[0] = pnt->nti.nai.szAtsLen + 1; // ISO14443-4 says that ATS contains ATS_Lenght as first byte + pbtOutput[0] = pnt->nti.nai.szAtsLen + 1; // ISO14443-4 says that ATS contains ATS_Length as first byte if(pnt->nti.nai.szAtsLen) { memcpy(pbtOutput+1, pnt->nti.nai.abtAts, pnt->nti.nai.szAtsLen); } diff --git a/examples/nfc-emulate-uid.1 b/examples/nfc-emulate-uid.1 index 7dfdce3..f98908b 100644 --- a/examples/nfc-emulate-uid.1 +++ b/examples/nfc-emulate-uid.1 @@ -7,7 +7,7 @@ nfc-emulate-uid \- NFC target emulation command line tool based on libnfc .RI [ UID ] .SH DESCRIPTION .B nfc-emulate-uid -is a tag emulation tool that allows to choose any tag UID. Tag emulation is one +is a tag emulation tool that allows one to choose any tag UID. Tag emulation is one of the main added features in NFC. But to avoid abuse of existing systems, manufacturers of the NFC controller intentionally did not support emulation of fully customized UID but only of "random" UIDs, which always start with 0x08. diff --git a/libnfc/chips/pn53x-internal.h b/libnfc/chips/pn53x-internal.h index 7861091..adc13bd 100644 --- a/libnfc/chips/pn53x-internal.h +++ b/libnfc/chips/pn53x-internal.h @@ -76,8 +76,8 @@ /** @note PN53x's normal frame: * * .-- Start - * | .-- Packet lenght - * | | .-- Lenght checksum + * | .-- Packet length + * | | .-- Length checksum * | | | .-- Direction (D4 Host to PN, D5 PN to Host) * | | | | .-- Code * | | | | | .-- Packet checksum @@ -91,8 +91,8 @@ * * .-- Start * | .-- Fixed to FF to enable extended frame - * | | .-- Packet lenght - * | | | .-- Lenght checksum + * | | .-- Packet length + * | | | .-- Length checksum * | | | | .-- Direction (D4 Host to PN, D5 PN to Host) * | | | | | .-- Code * | | | | | | .-- Packet checksum @@ -103,7 +103,7 @@ */ /** - * Start bytes, packet lenght, lenght checksum, direction, packet checksum and postamble are overhead + * Start bytes, packet length, length checksum, direction, packet checksum and postamble are overhead */ // The TFI is considered part of the overhead # define PN53x_NORMAL_FRAME__DATA_MAX_LEN 254 diff --git a/libnfc/drivers/acr122_usb.c b/libnfc/drivers/acr122_usb.c index fa4a8a5..b4473c0 100644 --- a/libnfc/drivers/acr122_usb.c +++ b/libnfc/drivers/acr122_usb.c @@ -508,7 +508,7 @@ acr122_usb_send (nfc_device *pnd, const uint8_t *pbtData, const size_t szData, c 0x00, // len 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // padding 0xff, 0x00, 0x00, 0x00, - 0x00, // pn532 command lenght + 0x00, // pn532 command length 0xd4, // direction }; size_t szFrame = acr122_build_frame (abtFrame, sizeof(abtFrame), pbtData, szData); diff --git a/utils/nfc-emulate-forum-tag4.c b/utils/nfc-emulate-forum-tag4.c index c89453a..f8f6158 100644 --- a/utils/nfc-emulate-forum-tag4.c +++ b/utils/nfc-emulate-forum-tag4.c @@ -91,7 +91,7 @@ uint8_t nfcforum_capability_container[] = { // Notes: // - I (Romuald) don't know why Nokia 6212 Classic refuses the NDEF message if MLe is more than 0xFD (any suggests are welcome); // - ARYGON devices doesn't support extended frame sending, consequently these devices can't sent more than 0xFE bytes as APDU, so 0xFB APDU data bytes. -// - I (Romuald) don't know why ARYGON device doesn't ACK when MLe > 0x54 (ARYGON frame lenght = 0xC2 (192 bytes)) +// - I (Romuald) don't know why ARYGON device doesn't ACK when MLe > 0x54 (ARYGON frame length = 0xC2 (192 bytes)) 0x00, 0xFF, /* MLc Maximum C-ADPU data size */ 0x04, /* T field of the NDEF File-Control TLV */ 0x06, /* L field of the NDEF File-Control TLV */ diff --git a/utils/nfc-mfultralight.1 b/utils/nfc-mfultralight.1 index da27ae3..93c49ec 100644 --- a/utils/nfc-mfultralight.1 +++ b/utils/nfc-mfultralight.1 @@ -8,7 +8,7 @@ nfc-mfultralight \- MIFARE Ultralight command line tool .SH DESCRIPTION .B nfc-mfultralight -is a MIFARE Ultralight tool that allows to read or write +is a MIFARE Ultralight tool that allows one to read or write a tag data to/from a .IR DUMP file. diff --git a/utils/nfc-read-forum-tag3.c b/utils/nfc-read-forum-tag3.c index 06721c3..72d9ee5 100644 --- a/utils/nfc-read-forum-tag3.c +++ b/utils/nfc-read-forum-tag3.c @@ -273,7 +273,7 @@ main(int argc, char *argv[]) fprintf (message_stream, "NFC Forum Tag Type 3 capacity: %d bytes\n", available_block_count * 16); uint32_t ndef_data_len = (data[11] << 16) + (data[12] << 8) + data[13]; - fprintf (message_stream, "NDEF data lenght: %d bytes\n", ndef_data_len); + fprintf (message_stream, "NDEF data length: %d bytes\n", ndef_data_len); uint16_t ndef_calculated_checksum = 0; for (size_t n = 0; n < 14; n++) diff --git a/utils/nfc-relay-picc.1 b/utils/nfc-relay-picc.1 index 29d29b0..a4a8be0 100644 --- a/utils/nfc-relay-picc.1 +++ b/utils/nfc-relay-picc.1 @@ -46,10 +46,10 @@ Remote relay over TCP/IP: \fBsocat\fP TCP-LISTEN:port,reuseaddr - "EXEC:\fBnfc-relay-picc -i\fP,fdin=3,fdout=4" + "EXEC:\fBnfc-relay-picc \-i\fP,fdin=3,fdout=4" \fBsocat\fP TCP:remotehost:port - "EXEC:\fBnfc-relay-picc -t\fP,fdin=3,fdout=4" + "EXEC:\fBnfc-relay-picc \-t\fP,fdin=3,fdout=4" .SH NOTES There are some differences with \fBnfc-relay\fP: