1. Reworded the introduction to the dependency management section.   Attempted to simplify and move away from 'we'.   It isn't that I suggest avoiding 'we' entirely, I use it myself, but if you use 'we' too much in a user manual it starts to sound a bit 'cultish'.

2. Filed out the intro paragraph a bit

3. Rewrote most of the introduction.  The itemized list wasn't really a list, so I've changed it to be a bit more obvious that this is listing major highlights of the feature.   I've also added some explanation at the end of the introduction to reinforce the core idea of Gradle:  We support strong conventions, but we give you the freedom to innovate how you see fit.

4. More polish to the introduction.   One important change was to move the compatibility line items for Gradle to the end of the highlighted feature list.  I think that Gradle needs to move away from comparing itself to Maven as a leading argument.  This might have made more sense in the beginning of the project, but Gradle is now able to stand on its own merits without having to remind the reader of this other build tool.

5. Worked on rewording and catching language issues through the dependency management subsection of the recommended rules in the user guide.

6. Finished rewording of the intro rules section

7. Reordered sections in the dependency management introduction.   The "Dependency Management in Java" was not appropriate where it was in the original document because it fell at the end of a list of Rules.   I've also added a section into the introduction that places special emphasis on the usefulness of Gradle during a build migration.