Naw, it’s gibberish to me as well.
If I were your husband, I’d try for a straight hourly rate. If the book is anything like the assignment description you posted, your husband better have a LOT of free time. Try for something in the range of $20-$40/hour. Hell, go for more, if they’re willing. But I think $20-$40 is typical of this type of work.
Some things for your husband to think about before he starts:
Consistency: This is one of the most important things to think about. Decide on a style and keep it the same throughout the book. Think about how he’ll do stuff like alternative definitions (ie: “The File Allocation Table, also known as FAT” vs “The File Allocation Table (FAT)” vs “The File Allocation Table, or FAT”) and capitolization. If a word is capitalized one place in the text, make sure it’s capitalized everywhere.
Another tip: try for fewer words used in a clear, consice manner. I find that many beginning tech writers (me included) tend to put extra words in a sentence thinking it makes things more clear. Hell, I sometimes even put whole sentences in! Try to edit out things like:
“The Web provides many links to FAQs, tutorials, and other information of interest to beginning tech writers” reads much better as “The Web provides links to FAQs, tutorials, and other information of interest to beginning tech writers.”
Also watch your wording. I first wrote that example as “The Web provides resources for beginning tech writers” but then you get into questions like “what do I mean by resources?” and “does the Web really provide those resources, or does it just provide links to resources that people have published on the Web.” In fact, I would probably end up rewriting that whole sentence to something like “A beginning tech writing can find FAQs, tutorials, and other helpful information on the Web.”
Another hint: You almost never need to start a sentence with “There”. ie “There are many resources on the Web for beginning tech writers.” It sounds cludgy, and adds extra words to the sentence. 99% of the time it can be edited out and the sentence flows better.
What else? Make sure your punctuation is correct. I’m currently reviewing a set of documents where the writer put in commas, just about everywhere. Like I’m demonstrating, here. He also really liked colons and semicolons; they’re almost always useless.
Anyway, that’s probably more information than you needed. Good luck to your husband - tech writing is a really good way to find out that what you thought were good writing skills could use some work. There’s a lot of people on this board MUCH more experienced than I who could probably give better tips, so if he needs any help, I’m sure he’ll find some!
Athena (“The Straight Dope is a good resource for beginning tech writers”)