 editing documentation embedded into drupal besides the handbook on drupalorg there is also some drupal documentation that is embedded in the drupal source code and visible from the administration pages of a drupal site this includes help pages for modules help text displayed at the top of administration pages and descriptive text within administration pages eg help text for a setting field because embedded documentation is part of the drupal source code the process for helping out with writing and editing this embedded documentation is slightly more complex than for editing pages on drupalorg here are some ways to help out test drupal for text issues during the development of a new drupal version download the new version from http drupalorg project drupal  install it and look over the help screens and user interface text if you find something that should be fixed in a help screen or other embedded help text file an issue even if you do not know how to create a patch you can still give before after text suggestions and someone else can create the patch to file an issue log in to drupalorg create an issue via the create content link  http drupalorg node add projectissue  choose drupal as the project choose the drupal version note that it s really only possible to change user interface text help text and other explanations in the version of drupal that is under development stable releases have been translated into other languages so their user interface text is almost never changed choose component documentation if the issue is in a help screen or user interface text if it is user interface text or choose the module that the issue pertains to as the component tag the issue with uitext or help text as appropriate choose category bug report text being wrong missing or unclear is a bug not a feature request or task make up a clear title and description and submit your issue help with existing issues use the advanced search for issues in the drupal project  http drupalorg project issues search drupal  and look for component documentation or user interface text or search for tags help text or uitext be aware that most of the issues filed under component documentation are issues with the inline programmer api documentation of functions in the source code displayed on apidrupalorg so if you are not a programmer these will not be things you will probably want to work on even if you cannot write patches you can still review patches and make suggestions on how to improve text by commenting on issues some tips on using the issue queue look for issues whose status is active or needs work if you want to write some documentation or code look for needs review issues if you want to review what others have done an excellent place to start if you are new to drupal issues and a vitally important part of the process even if you are not a programmer you can still review patches find an issue that has status needs review scroll down to the bottom of the issue s comments and find the latest patch attachment click on the attachment to see it the lines with are being added lines with are being removed some patches will also have a screen shot making reviewing even easier if you think a patch is good add a comment saying what part you reviewed and that you thought it was good if you think your review was comprehensive or if several people have commented that it s a good patch and you think the coverage overall is comprehensive enough change the issue s status to reviewed and tested by the community also known as rtbc if you think a patch needs some work change the status of the issue to needs work and add a specific comment about what you think should be changed if possible with a suggestion of what to change it to please try to be constructive if the issue you are looking at doesn t yet have a patch you can either make one or add suggestions as to what the text should say someone else can read your suggestions and make a patch if you attach a patch file be sure to change the status of the issue to needs review so others can test and review your patch and above all don t take anything in the issue queue personally the intent of the issue queue is to provide a forum for discussion on how to make drupal better so try to take any comments on your patches as constructive comments and thoughtful discussion even if not everyone writes their comments in this way  demo articles 