From 867650b71eb84234ab49c85e3fe3c4d3129779b8 Mon Sep 17 00:00:00 2001
From: sp2xdev <127630192+sp2xdev@users.noreply.github.com>
Date: Sun, 12 Jan 2025 05:15:03 -0800
Subject: [PATCH] Updated Known issues (markdown)

---
 Known-issues.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Known-issues.md b/Known-issues.md
index 34ff3dc..b100e72 100644
--- a/Known-issues.md
+++ b/Known-issues.md
@@ -298,7 +298,7 @@ As mentioned above, many clones of ACR112U fail to properly read FeliCa cards. W
 
 ... and not actually read the card contents.
 
-Instead of finding a good ACR112U unit, you may instead want to look into DIY solutions based on cardIO HID protocol: https://rhythm-cons.wiki/other-hardware/card-readers/
+Instead of trying to find a good ACR112U unit, you may instead want to look into DIY solutions based on cardIO HID protocol: https://rhythm-cons.wiki/other-hardware/card-readers/
 
 There is also a known bug in ACR122U logic (`scard.cpp`) when reading UID values from cards. It interprets the "success" header `90 00` as part of the UID. If your card has UID of `1234 5678` then it's read as `1234 5678 9000 0000`. This is not an issue for FeliCa as they already have full 8 bytes of UID, it's only a problem for cards with UID < 8 bytes. It's recommended that you set `-scardfix fix` for more correct behavior for non-FeliCa cards.