I can't provide exactly what you're looking for, but I would disagree with outright repetition as a means of learning to do any kind of writing. If you repeat b

I can't provide exactly what you're looking for, but I would disagree with outright repetition as a means of learning to do any kind of writing. If you repeat bad practices due to inexperience you will be training to a bad job with confidence. Hemingway said that being a good writer means being a dedicated reader and that reading is the activity of training to write (heavily paraphrased from A Moveable Feast). If you want to write good technical documentation, there is nothing that will prepare you as well as experiencing the difference between good and bad examples. If you can get your hands on some real-world examples of what you want to write then you will develop a critical eye as you read them. I am sure that there are some that would make you eager to throw your money in the ring and there are probably some that would embarrass you if you were a part of the pitch. For a more minute suggestion, look into cognitive ease and how it is affected by language (Thinking Fast and Slow by Daniel Kahneman is a personal and HN favorite). If you are trying to be persuasive, don't use weird words like people do when they are writing their first resume, forgo words that you have trouble pronouncing and use jargon judiciously to inspire a positive and confident reaction. Also, here's a Quora thread[1] that suggests the exact opposite approach and also gives a book recommendation. While I disagree with that advice it may not matter because, as pointed out there, these documents are proprietary. 1. https://www.quora.com/Where-can-I-view-real-world-business-plans-not-sample-plans https://www.quora.com/Where-can-I-view-real-world-business-p...