Please aim to keep lines in an XML file around 80 characters long or less. This is a loose requirement and 100 is probably acceptable as a maximum length. This aids in keeping diffs simple, which is particularly useful for translators, so follow this rule carefully.
For XML, indent using one space. Do not use tabs. PHP code, in examples, uses four spaces for indentation, since the code should adhere to the PEAR Coding Standards.
Punctuation in the PHP Manual follows regular grammatical rules. When writing flowing sentences, such as in function descriptions, normal punctuation should be used. Lists, titles, and sentence fragments should not be punctuated with a period. Sentences need not have two spaces between them. Commas and apostrophes should be used appropriately.
The PHP Manual is a technical document, and should be written so. The use of "you" is rampant in the manual, and presents an unprofessional image. The only exceptions to the personalization rule are: the PHP Tutorial and FAQs.
INCORRECT: You can use the optional second parameter to specify tags that should not be stripped. CORRECT: The optional second parameter may be used to specify tags that should not be stripped.
The PHP Manual should be written with particular attention to general English grammar. Contractions should be used appropriately. Special attention should be applied to sentence construction when using prepositions (i.e., sentences should not end in prepositions).
Various non-english, technical terms are used throughout the PHP Manual, without clear indication of their appropriate spelling. The following list clears up this issue:
|Appropriate Use||Inappropriate Use(s)|
|any way||anyway, anyways|
|built-in||built in, builtin|
|Linux||linux, nx, nix, nux, etc|
|PHP 5||PHP5, PHP-5|
|PHP 4.3.0||PHP 4.3, PHP 4.3.0RC2, PHP 5.0.0BETA, PHP 4.3.0PL1|
|superglobals||super globals, autoglobals|
|the Foo Page||click here, go here|
|Unix||UNIX (it's a registered trademark)|
|Windows||windows (when referring to Microsoft Windows)|