From c42e2502d4627d3ea62f83c32677b100bb3cebdc Mon Sep 17 00:00:00 2001 From: rstular Date: Sun, 28 Apr 2019 09:41:04 +0200 Subject: [PATCH] Fixed a typo in examples/nfc-emulate-uid.1 --- examples/nfc-emulate-uid.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/nfc-emulate-uid.1 b/examples/nfc-emulate-uid.1 index f0e2164..a731bfc 100644 --- a/examples/nfc-emulate-uid.1 +++ b/examples/nfc-emulate-uid.1 @@ -14,7 +14,7 @@ fully customized UID but only of "random" UIDs, which always start with 0x08. The nfc-emulate-uid tool demonstrates that this can still be done using transmission of raw frames, and the desired UID can be optionally specified. -This makes it a serious thread for security systems that rely only on the +This makes it a serious threat for security systems that rely only on the uniqueness of the UID. Unfortunately, this example can't directly start in fully customisable