First of all, you expanded emunand and rednand and other similar technical words to inflate the word count, which looks rather cheap and forced. Even with that, you have written only 277 words, including the title.
Second, "writing a modified version of a9lh which includes permanent SaltFW custom firmware" part is wrong. What I'm writing is another modified Luma to be included in stage2 of A9LH process.
And third, you said SaltFW doesn't have these, so let's take a look at the list, with explanations:
- extended firmware.bin support: This is 100% supported, proof: http://i.imgur.com/Bs8SC3X.png)
- using devices with lower native firmwares (Also 100% supported, it's possible to boot 9.x firmware with SaltFW 2.0b
- anti-downgrade checks: I think you meant Luma's anti-downgrade checks patching, which's not needed since all you have to do to have this in SaltFW is to drop firmware.bin to the root of your SD
- development version: Not needed or planned, as developer version literally prevents people from accessing eShop and other online nintendo features, however I'll be adding debug info in the next release.
- chainloader: This is a decision on my end to keep it clean. It's a "Custom Firmware", not a "custom bootloader". I personally use CTRBootManager9 to manage my payloads, which not only is capable of button shortcuts, but also has a nice GUI I can choose things from, and even can load files that I haven't put in its config file beforehand with its nice file browser function.
Final words: Not only did you inflate your word count by having a whooping 101 words in your introduction paragraph that had very little relation to SaltFW, you also expanded technical terms that should not have been, AND you did not even do your research on neither ShadowNAND, nor SaltFW.
All in all, I'm astounded to have read your essay. I can't wait for the remaining 232 words in part 2.
(my response was 316 words, and I did not even expand anything. And no, I'm not a native speaker.)