updated, word "non" to "none"

* Spelling updated at LTESniffer/README.md line #9

README.md

@@ -6,7 +6,7 @@
 It first decodes the Physical Downlink Control Channel (PDCCH) to obtain the Downlink Control Informations (DCIs) and Radio Network Temporary Identifiers (RNTIs) of all active users. Using decoded DCIs and RNTIs, LTESniffer further decodes the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) to retrieve uplink and downlink data traffic.
 
 LTESniffer supports an API with three functions for security applications and research. Many LTE security research assumes
-a passive sniffer that can capture privacy-related packets on the air. However, non of the current open-source sniffers satisfy their requirements as they cannot decode protocol packets in PDSCH and PUSCH. We developed a proof-of-concept security API that supports three tasks that were proposed by previous works: 1) Identity mapping, 2) IMSI collecting, and 3) Capability profiling.
+a passive sniffer that can capture privacy-related packets on the air. However, none of the current open-source sniffers satisfy their requirements as they cannot decode protocol packets in PDSCH and PUSCH. We developed a proof-of-concept security API that supports three tasks that were proposed by previous works: 1) Identity mapping, 2) IMSI collecting, and 3) Capability profiling.
 
 Please refer to our [paper][paper] for more details.
 
@@ -287,4 +287,4 @@ To sniff the uplink traffic, LTESniffer requires USRP X310 with 2 daughterboards
 [capture-readme]: https://github.com/SysSec-KAIST/LTESniffer/tree/LTESniffer-record-subframe
 [cellular77]: https://github.com/cellular777
 [Cemaxecuter]: https://www.youtube.com/@cemaxecuter7783
-[Ksk190809]: https://github.com/Ksk190809
+[Ksk190809]: https://github.com/Ksk190809