3.1 - Intro - Clarity and Organization Improvements

[Patrick Burke]

I'd like to change the intro from this:
If you followed the instructions to get set up with Ubuntu Development, you should be all set and ready to go.
(process to fix a bug image)
As you can see in the image above, there is no surprises in the process of fixing bugs in Ubuntu: you found a problem, you get the code, work on the fix, test it, push your changes to Launchpad and ask for it to be reviewed and merged. In this guide we will go through all the necessary steps one by one.

to this:
Once you're done Getting Set Up, you're ready to learn how to start fixing bugs.
<process to fix a bug image>
As you can see in the image above, the process of fixing bugs in Ubuntu is very simple:
 1) You find a problem
 2) You retrieve the relevant Ubuntu source code
 3) You fix the problem in the Ubuntu source code
 4) You test your fix
 5) You push your changes to Launchpad and ask for it to be reviewed, then merged.
In this guide, we will guide you through those steps.

This would improve readability of the section.

Additionally, 3.3 through 3.6 come between step 1 (find problem) and step 2 (retrieve code). I'd like to make these sections sub-sections of 3.2.

[Patrick Burke (tabbycat45)]

I'd like permission from the docs team (or Ubuntu Packaging Guide team?) to fix this error.

This is my first bug I've opened or worked on. So I am at step 3.6 (Offering Help) of the bug resolution process. Thank you in advance.

[Dmitry Shachnev (mitya57)]

Merge proposals against lp:ubuntu-packaging-guide Bzr branch are welcome!