Whitespace cleanup + use <section> instead of <sect[12]>.

Translators can safely ignore this commit.

en_US.ISO8859-1/articles/problem-reports/article.sgml

@@ -27,7 +27,7 @@
 
   <indexterm><primary>problem reports</primary></indexterm>
 
-  <sect1 id="pr-intro">
+  <section id="pr-intro">
     <title>Introduction</title>
 
     <para>One of the most frustrating experiences one can have as a
@@ -54,9 +54,9 @@
       chronologically, so you should read through the entire document
       before submitting a problem report, rather than treat it as a
       step-by-step tutorial.</para>
-  </sect1>
+  </section>
 
-  <sect1 id="pr-when">
+  <section id="pr-when">
     <title>When to submit a problem report</title>
 
     <para>There are many types of problems, and not all of them should
@@ -115,9 +115,9 @@
       does mean that the chances of your problem report ever leading
       to a bug fix are very slim, and you should consider letting the
       matter drop.</para>
-  </sect1>
+  </section>
 
-  <sect1 id="pr-prep">
+  <section id="pr-prep">
     <title>Preparations</title>
 
     <para>A good rule to follow is to always do a background search
@@ -180,9 +180,9 @@
       submit your problem report, there is a good chance that it will
       go unnoticed for a while, until someone re-categorizes
       it.</para>
-  </sect1>
+  </section>
 
-  <sect1 id="pr-writing">
+  <section id="pr-writing">
     <title>Writing the problem report</title>
 
     <para>Now that you have decided that your issue merits a problem
@@ -192,7 +192,7 @@
       environment variable is set to something sensible, and run
       &man.send-pr.1;.</para>
 
-    <sect2>
+    <section>
       <title>Attaching patches or files</title>
 
       <para>The &man.send-pr.1; program has provisions for attaching
@@ -218,9 +218,9 @@
 	specify otherwise in your PR, any patches you submit will be
 	assumed to be licensed under the same terms as the original
 	file you modified.</para>
-    </sect2>
+    </section>
 
-    <sect2>
+    <section>
       <title>Filling out the template</title>
 
       <para>The template consists of a list of fields, some of which
@@ -466,9 +466,9 @@
 	    leave this field blank than to speculate.</para>
 	</listitem>
       </itemizedlist>
-    </sect2>
+    </section>
 
-    <sect2>
+    <section>
       <title>Sending off the problem report</title>
 
       <para>Once you are done filling out the template, have saved it,
@@ -488,11 +488,11 @@
 
       <para>This will read the specified file, validate the contents,
 	strip comments and send it off.</para>
-    </sect2>
+    </section>
 
-  </sect1>
+  </section>
 
-  <sect1 id="pr-followup">
+  <section id="pr-followup">
     <title>Follow-up</title>
 
     <para>Once your problem report has been filed, you will receive a
@@ -516,9 +516,9 @@
       gone away, just send a follow-up (in the manner prescribed
       above) saying that the problem report can be closed, and, if
       possible, explaining how or when the problem was fixed.</para>
-  </sect1>
+  </section>
 
-  <sect1 id="pr-further">
+  <section id="pr-further">
     <title>Further Reading</title>
 
     <para>This is a list of resources relevant to the proper writing
@@ -540,5 +540,5 @@
 	  developers.</para>
       </listitem>
     </itemizedlist>
-  </sect1>
+  </section>
 </article>