You should ask yourself “why am I writing this document“, and then check to see if the document is achieving your goals. I am guessing your goal is “I want to serve as the definitive publicly available textbook for the Xbox 360.“. If that’s your goal, I would split the doc into chapters by topic, and then edit the heck out of each chapter. Look at a model textbook like Computer Architecture, a Quantitative Approach, and see if you can imitate their style.
I think a good technical editor could help you edit this down to about 25% of the words, and still cover the same information.
The job is too big for drive-by code review style comments. You’re going to have to put in the work yourself if you want to improve this.
Comments
Your heart is clearly invested in this project. But compare the wordiness of your doc to a primary source like https://old.hotchips.org/wp-content/uploads/hc_archives/hc17...
You should ask yourself “why am I writing this document“, and then check to see if the document is achieving your goals. I am guessing your goal is “I want to serve as the definitive publicly available textbook for the Xbox 360.“. If that’s your goal, I would split the doc into chapters by topic, and then edit the heck out of each chapter. Look at a model textbook like Computer Architecture, a Quantitative Approach, and see if you can imitate their style.
I think a good technical editor could help you edit this down to about 25% of the words, and still cover the same information.
The job is too big for drive-by code review style comments. You’re going to have to put in the work yourself if you want to improve this.