From f60b4e410c1408acd0e0b09e55e624d509b31aa1 Mon Sep 17 00:00:00 2001 From: Arttu mahlakaarto Date: Sat, 8 Feb 2020 15:36:11 +0200 Subject: [PATCH] Fixing a small typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index af38bfe..f13a0b2 100644 --- a/README.md +++ b/README.md @@ -464,7 +464,7 @@ P4wnP1_cli hid run -c 'waitLED(NUM); type("A huge amount of characters\n")' If you tested the command above, typing should only start if NUM LOCK is pressed on the USB host's hardware keyboard, but you might encounter cases where the keystrokes immediately are issued, even if NUM LOCK wasn't pressed (and the -keyboard LED hasn't hacnged). +keyboard LED hasn't changed). This is intended behavior and the reason for this is another use case for the `waitLED` command: