This is a good rough draft but it lacks a lot of basic background information. It reminds me of trying to teach programming by only providing a collection of code snippets, these are useful but they won't replace true guidance and they can become a dangerous learning crutch. Don't forget who your audience is (or who you're attracting with a title like Web Hacking 101) and remember that when you write you should be focusing on making it as easy to read and understand as easy as possible for them. Explain the whys behind taking certain steps such as why you should be google searching for sql errors (saves you time, it's easy, google cache pages can show details about errors that are not longer visible on the live site, and most importantly what sql is and the implications of an error).<p>While it's not about technical writing I think Kurt Vonnegut's advice will help you to make a better write up. Specifically #7. -- Pitty the Readers[0]<p>Vonnegut mentions The Elements of Style[1] which you'll find useful if you're struggling to give detailed explanations<p>[0] <a href="http://peterstekel.com/PDF-HTML/Kurt%20Vonnegut%20advice%20to%20writers.htm" rel="nofollow">http://peterstekel.com/PDF-HTML/Kurt%20Vonnegut%20advice%20t...</a><p>[1] <a href="http://faculty.washington.edu/heagerty/Courses/b572/public/StrunkWhite.pdf" rel="nofollow">http://faculty.washington.edu/heagerty/Courses/b572/public/S...</a>