Use headings on the project page

I find the project page as proposed more readable. The list made probably more sense when the list items were fewer → , and they did not appear as a wall of text like now.

I would just avoid adding "or the Report as spammer link shown in user profiles" because in most of the cases what needs to be reported is a post or a comment, for which the Report as spammer link does not help much. It just adds a link to the user account in a view; site moderators then need to check all the comments or posts created using that account to find what needs to be deleted as spam.

Thanks, I'm glad you found it easier to read. As for that spam, I only added formatting, that part about spam is already on the page. If that needs to be changed, I trust you know better than me what it should be.

This is the markup I used in the new revision.

This is the main project for all <a href="http://drupal.org/documentation">Drupal documentation</a>, except contributed projects. For contributed projects create an issue in the issue queue for that project.

To learn more about helping with documentation efforts, start with the <a href="http://drupal.org/contribute/documentation">Contribute to documentation</a> section of the handbook.

<p>You can report issues regarding documentation in the following places:</p>

<h3>About the documentation "infrastructure" (software tools for creating, editing, maintaining, locating, and reading the documentation on Drupal.org)</h3>
<p>Create an issue in the <a href="http://drupal.org/node/add/project-issue/documentation" rel="nofollow">Documentation project issue queue</a> and use the <strong>Docs infrastructure</strong> component.</p>

<h3>About documentation procedures and policies</h3>
<p>Create an issue in the <a href="http://drupal.org/node/add/project-issue/documentation" rel="nofollow">Documentation project issue queue</a> and use the <strong>Policies and Procedures</strong> component.</p>

<h3>API (api.drupal.org)</h3>
<p>Create an issue in the <a href="http://drupal.org/node/add/project-issue/drupal" rel="nofollow">Drupal Core project issue queue</a> and use the <strong>documentation</strong> component. The only exception is a few files, such as the Form API reference, which are actually here in the Documentation git repository.</p>

<h3>User interface text within Drupal core itself</h3>
<p>Create an issue in the <a href="http://drupal.org/node/add/project-issue/drupal" rel="nofollow">Drupal Core project issue queue</a> and use the <strong>user interface text</strong> component.</p>

<h3>Contributed project</h3>
<p>Create an issue in the issue queue for that project.</p>

<h3>Spam</h3>
<p>Use the <em>report spam</em> link shown for comments and nodes.</p>

<h3>For any other issue with the Drupal.org online Community Documentation</h3>
<p>Create an issue in the <a href="http://drupal.org/node/add/project-issue/documentation" rel="nofollow">Documentation project issue queue</a> or, better yet, just edit the page.</p>

Thanks, I think that is an improvement. Others may have further ideas but I am OK with closing this issue.