typo

README.md

@@ -21,7 +21,7 @@ an older connector (mini PCI) that is available on many more tested and validate
   - More generally, the WPJ428 board is not really amazing: it is targeted at "IoT" which is really a diverted way to say that is really "underpowered" in many aspects. Due to its niche target market, it was not well supported by OpenWRT, especially just after it's release. And of course, we bought it "just after its release".
   - The firmware of our LTE/NR5G modem is very buggy. Avoid obscure references and, instead, choose already widespread references.
 Also, the market does not move at the same pace: while many smartphone are sold with support from NR5G, 
-pluggable modems where only at the beggining and we paid the "early adopter" tax here.
+pluggable modems were still nascent, here again we paid the "early adopter" tax, with the UDP bug for example.
   - The support for LTE/NR5G is not optimal in OpenWRT. ModemManager is a great quality of life enhancer, but it is meant to work with NetworkManager, which is not integrated with OpenWRT. We had to write multiple flawed scripts to handle re-connections and the various quirks associated to mobile connections. Ideally, we should have written a daemon in a proper programming language (C or Lua) that observe/interact with ModemManager/NetworkManager through their dbus interface for a more reliable experience.
   - We did not invest enough time/energy on the antenna part. Having a clear line of sight and putting it above (and not below) the roof would have clearly improved performances. Also, your connection quality will heavily depend on your mobile provider's cell tower, and not all cell tower are born equals. Some of them are connected with fiber directly to the backbone, some of them are "meshed" through wireless connection with other ones. Some of them are also very overloaded, while other ones have only you as the client. Etc. Collecting information beforce deploying your router is very crucial.