Goal: 
Locate an issue that reports a documentation problem. Edit the documentation to resolve the problem.
Skills required: 
Editing (English)
Technical writing (English)
Background and reference information: 
Creating or updating an issue report
Find the issues for a project
Detailed steps: 
  1. Set up prerequisites: Log in and optionally Confirmed account (only needed for creating new documentation pages) from Common Prerequisites for Contributors.
  2. Browse through the Documentation issue list, and find an issue to work on that interests you. The issue Status should be either Active, Needs Review, or Needs Work. If you want to do some documentation writing, look for issues whose component is "Missing documentation". If you want to edit existing documentation, look for issues whose component is "Correction/Clarification". If you have an interest in a particular contributed project (module, theme, or distributions), you could also look for issues in that project with component "Documentation" (see Find the issues for a project).
  3. Read the issue, and follow the steps in the Triage a Documentation issue task writeup to verify that it is a valid Documentation issue with the correct status, component, and project. If you find out that it isn't, return to the first step and find another issue to work on. Also, if someone else has recently commented that they are working on the issue, find another one to work on.
  4. If the issue status is "Needs work" or "Active" and you know how to resolve the problem described in the issue:
    • If the changes will take you significant time to complete, add a comment to the issue saying you are working on it, and when you plan to complete the work, so that others will know your plans.
    • Edit the relevant documentation page(s) to fix the issue. Refer to the Drupal.org content style guide.
    • When you are finished, change the issue status to Fixed, and add a comment explaining your changes, linking to the pages you updated in your comment. Alternatively, if you have made major changes and would like someone else to review the changes, change the issue status to "Needs review".
  5. If the issue status was already "Needs review", then someone has made a change and they would like someone else to review their changes:
    • You can see the change history for a page by clicking "View history" in the green drop-down action button near the top of a documentation page; there are links in the history list to compare revisions. So, click links to documentation pages that were updated or created, and review the changes.
    • If the changes look good and the issue is resolved, change the issue status to Fixed and add a comment saying what you reviewed.
    • If the changes are mostly good but some minor edits are needed, you can make the edits, and then change the issue status to Fixed and add a comment saying what you reviewed and edited.
    • If the changes need more extensive work than you can do, change the issue status to "Needs work" and add a comment explaining what needs to be updated.