We need to update this page to document the new per-package clouds: http://confluence.atlassian.com/display/CLOVER/About+%27Coverage+Clouds%27

You may want to check with Brendan and Nick to ensure they are happy with the current implementation (you're on the review but it might be quicker just to ask them).

Text to be changed to:
======
'Coverage Clouds' provide an instant overview of your entire project and individual packages, enabling you to identify areas of your code that pose the highest risks or shortcomings.Each Coverage Cloud displays two metrics per Java Class. One metric is displayed via the font size, and the other via the font color. Each attribute has relative weighting across the entire project. Classes are sorted alphabetically.

...

Project Risks / Package Risks

The Project Risks / Package Risks Cloud highlights those classes that are the most complex, yet are the least covered by your tests. The larger and redder the class, the greater the risk that class poses for your project or package. Package risk clouds can be toggled to include or exclude classes in sub-packages

...

Quick Wins

This Cloud highlights the "low hanging coverage fruit" of your project or package. You will achieve the greatest increase in overall project or package coverage by covering the largest, reddest classes first. Package Quick Win clouds can be toggled to include or exclude classes in sub-packages.
=====

The image currently shows the Eclipse plugin's clouds. We should instead show coverage clouds for Checkstyle or some other OSS project. A per-package (with sub packages toggle) and a per-project cloud should be shown.