Attempt to reduce the number of white-space changes

Author: ramsey

license/contrib-guidelines-code.php

@@ -6,27 +6,33 @@
 <h2>PHP Contributor Guidelines for Code Developers</h2>
 
 <p>
-    Before you contribute code to PHP, you must understand and accept the principles under which PHP itself is
-    developed. These are summarized in the next paragraph.
+  Before you contribute code to PHP, you must understand and accept the
+  principles under which PHP itself is developed. These are summarized in the
+  next paragraph.
 </p>
 
 <p>
-    Any code contributed to PHP must be contributed under the terms of the Modified BSD License or other compatible,
-    permissive license. PHP is distributed under the <a href="/license/#bsd-3-clause">Modified BSD License</a>. This
-    includes implementation code, test cases, utility scripts and tools&mdash;that is, all code associated with the PHP
-    project. If you contribute code that isn't entirely your own (for example, it may be partially derived from other
-    Open Source software), you should add a comment to the source code indicating the origin and license of the original
-    code. If you are unsure of the license, you must confirm with the owner that they grant permission to contribute it
-    to PHP under the terms of the Modified BSD License or other compatible license.
+  Any code contributed to PHP must be contributed under the terms of the
+  Modified BSD License or other compatible, permissive license. PHP is
+  distributed under the <a href="/license/#bsd-3-clause">Modified BSD
+  License</a>. This includes implementation code, test cases, utility scripts
+  and tools&mdash;that is, all code associated with the PHP project. If you
+  contribute code that isn't entirely your own (for example, it may be
+  partially derived from other Open Source software), you should add a comment
+  to the source code indicating the origin and license of the original code.
+  If you are unsure of the license, you must confirm with the owner that they
+  grant permission to contribute it to PHP under the terms of the Modified BSD
+  License or other compatible license.
 </p>
 
 <p>
-    Specifically regarding source code licensed under the GNU General Public License (GPL):
+  Specifically regarding source code licensed under the GNU General Public
+  License (GPL):
 </p>
 
 <ul>
-    <li>GPL-licensed code cannot be used as a basis for any work contributed to PHP.</li>
-    <li>Extensions which link to GPL-licensed libraries will not be accepted.</li>
+  <li>GPL-licensed code cannot be used as a basis for any work contributed to PHP.</li>
+  <li>Extensions which link to GPL-licensed libraries will not be accepted.</li>
 </ul>
 
 <?php site_footer();

license/distrib-guidelines-code.php

@@ -6,54 +6,55 @@
 <h2>PHP Code Distribution Guidelines</h2>
 
 <p>
-    The PHP code can be redistributed in source or binary form provided that
-    you respect the terms of the <a href="/license/#bsd-3-clause">license</a>.
+  The PHP code can be redistributed in source or binary form provided that
+  you respect the terms of the <a href="/license/#bsd-3-clause">license</a>.
 </p>
 <p>
-    In plain English, this means that you have to include the full license text
-    in human-readable form with every distributed copy of PHP, whether in source
-    or binary form. One way of doing this is to put a copy of the license in a
-    text file that you include with the source or binary package before distribution.
-    This ensures that the license information can be read properly even when a
-    binary is shipped instead of source code. A text file containing license and
-    copyright information is sometimes given the filename "Notice" or "NOTICE,"
-    and may be referred to as a "notice file."
+  In plain English, this means that you have to include the full license text
+  in human-readable form with every distributed copy of PHP, whether in source
+  or binary form. One way of doing this is to put a copy of the license in a
+  text file that you include with the source or binary package before
+  distribution. This ensures that the license information can be read properly
+  even when a binary is shipped instead of source code. A text file containing
+  license and copyright information is sometimes given the filename "Notice"
+  or "NOTICE," and may be referred to as a "notice file."
 </p>
 <p>
-    Some files in the PHP codebase have been contributed under other licenses.
-    If you want to distribute these files, you must also respect the terms of
-    their licenses. Look for the terms in the license/copyright comment block at
-    the top of the source file. Sometimes the license terms are included in a
-    separate license file in the same directory as the source file. The license
-    terms may require that its own license and copyright information be included
-    with every distributed copy (including binaries). This is a common requirement,
-    which may be satisfied by adding the appropriate license text to a text file
-    for distribution purposes, like the notice file suggested above.
+  Some files in the PHP codebase have been contributed under other licenses.
+  If you want to distribute these files, you must also respect the terms of
+  their licenses. Look for the terms in the license/copyright comment block at
+  the top of the source file. Sometimes the license terms are included in a
+  separate license file in the same directory as the source file. The license
+  terms may require that its own license and copyright information be included
+  with every distributed copy (including binaries). This is a common
+  requirement, which may be satisfied by adding the appropriate license text
+  to a text file for distribution purposes, like the notice file suggested
+  above.
 </p>
 <p>
-    A single notice file may list all the licenses and copyright information
-    applicable to the entire codebase you are distributing. It is good practice to
-    indicate which source file(s) a particular license applies to.
+  A single notice file may list all the licenses and copyright information
+  applicable to the entire codebase you are distributing. It is good practice
+  to indicate which source file(s) a particular license applies to.
 </p>
 
 <h3>Modified products derived from PHP</h3>
 
 <p>
-    You may distribute your own software product derived from PHP, in source or
-    binary form, provided that relevant copyright information and license(s) from
-    the PHP codebase are distributed in human-readable form with every copy, as
-    described above.
+  You may distribute your own software product derived from PHP, in source or
+  binary form, provided that relevant copyright information and license(s)
+  from the PHP codebase are distributed in human-readable form with every
+  copy, as described above.
 </p>
 <p>
-    In accordance with the <a href="/license/#bsd-3-clause">license</a>, you may
-    not use the name of any copyright holders or contributors to endorse or
-    promote products derived from PHP without specific prior written permission.
+  In accordance with the <a href="/license/#bsd-3-clause">license</a>, you may
+  not use the name of any copyright holders or contributors to endorse or
+  promote products derived from PHP without specific prior written permission.
 </p>
 <p>
-    Please do not use "PHP" in the names of products derived from PHP. This
-    creates confusion and implies a relationship between your product and the PHP
-    project that may not exist. However, you may indicate that your product works
-    with, is compatible with, or is intended for use with PHP.
+  Please do not use "PHP" in the names of products derived from PHP. This
+  creates confusion and implies a relationship between your product and the
+  PHP project that may not exist. However, you may indicate that your product
+  works with, is compatible with, or is intended for use with PHP.
 </p>
 
 <?php site_footer();