chore: amend readme

README.md

@@ -16,7 +16,7 @@ Furthermore, large parts of its firmware have also been taken from PhobGCC's fir
 
 </details>
 
-<details><summary>Firmware is written in Rust, using the [embassy-rs]() framework for asynchronous operations.</summary>
+<details><summary>Firmware is written in Rust, using the <a href="#">embassy-rs</a> framework for asynchronous operations.</summary>
 
 The firmware being written in Rust allows for writing much cleaner code than one would normally be used to when writing firmware in C, because Rust allows for many zero and low cost abstractions in order to enhance code readability and maintainability. Adding embassy-rs for asynchronous operations on top of that provides 2 main benefits:
 
@@ -27,6 +27,18 @@ The firmware being written in Rust allows for writing much cleaner code than one
 
 <details><summary>Provides both the lowest latency of any Switch controller, as well as the best input integrity.</summary>
 
+Because the NaxGCC connects directly to the console via USB, it already outperforms any controller that has to go throug an adapter in terms of input latency (including PhobGCC + Lossless Adapter).
+
+Further, the NaxGCC has a special "input consistency" mode (enabled by default), which ensures a $\gt 98\%$ input accuracy, compared to $\lt 75\%$ for any other controller (worse if there is an adapter in the mix, with the exception of the Lossless Adapter).
+
+For details on how it works, have a look at our wiki.
+
+</details>
+
+<details><summary>Compatible with Phob hardware.</summary>
+
+The NaxGCC firmware is compatible with regular Phob 2.0 boards (those using an RP2040 microcontroller), since it's originally forked from the PhobGCC project. This means that if you are willing and able to slightly modify your controller shell to allow a micro USB cable to connect to your Phob board during play, you can turn your existing PhobGCC into a NaxGCC at no extra cost!
+
 </details>
 
 ## Contributing