Re the manual:
there are quite a few document publishing software products available, some are still free. They make manual wiring and update so much easier than doing it by hand.
Also, use some standards, especially regarding text colors. For example, normal text is black on white (like paper) or some like white lettering on black backgroud. Automtic indexes and internal cross-references are handled aubomagically by the document creation software, and those links can all be set to one color or (more often) are underlined, bold, italics, or what-have-you. An example of that would be if you're looking up flight planning. "Flight planning" is highlighted in somr form or another, showing you that if you select that phrase, you get a popup that indicates in a scrolling window, all the other places it occurs in the manul. You can also automatically have thematic suggestions as well for each occurrence. The software handles all that for you, doing the drudgery donkey-work, which is why we use computers to begin with. And so on. Many, many options exist for manuals.
Lastly, with proper compression, you could get the entire Bible and all cross-referencing Concordance to store in just 3 bytes. Not to exaggerate any... True story: when the Navy changed the documentation requirements for the DD destroyers from paper to CD-ROM (back then) the ships literally rode almost 6 feet higher in the water. I bet the manuals could be fit into the iFly environemnts, including the 700 series of hardware products.
I just wish we could do the forums this way, too. So when someone asks a question, all relevant prior discussions about the subject would be made available and the poster given the choice of posting his new (old) question or not.
It would be great if the manual also included work and data flow diagrams for each major and minor function. Those are even easier than text to build. Makes a book into a graphical unit rather than purely text.