Hello again, Brain
As far as educating the customer on what exactly software development is and how it works: nope. Also nothing on change control processes etc.
I do understand their importance but they are heavily influenced by what your company/project size looks like: Are we talking about building stuff as a 1-2 person show for local acquaintances or are you building something for a Fortune500 and 300 people involved. Is it enough that you as the programmer-marketer drink a beer with your customer and tell him a bit about what software development is all about, or do you need to bring 100 people across different departments involved? Tricky topic, as the practical solutions will look completely different in each case.
But you are completely right with the general gist: If the customer is so far removed from tech (and I have been part of plenty of such projects) you have to educate him. Actually I could include notes on that in an update of the ebook. Thanks for noting, let me see what I can do