diff --git a/en_US.ISO8859-1/articles/problem-reports/article.sgml b/en_US.ISO8859-1/articles/problem-reports/article.sgml
index afdefa10a6..e99f3cba23 100644
--- a/en_US.ISO8859-1/articles/problem-reports/article.sgml
+++ b/en_US.ISO8859-1/articles/problem-reports/article.sgml
@@ -138,6 +138,25 @@
       or overheating processors — you should always try to rule
       out these causes, whenever possible, before submitting a PR.</para>
 
+    <para>Next, you need to make sure your problem report goes to the
+      right people.</para>
+
+    <para>The first catch here is that if the problem is a bug in
+      third-party software (a port or a package you have installed), you
+      should report the bug to the original author, not to the &os;
+      Project.  There are two exceptions to this rule: the first is if
+      the bug does not occur on other platforms, in which case the
+      problem may lie in how the software was ported to &os;; the
+      second is if the original author has already fixed the bug and
+      released a patch or a new version of his software, and the
+      &os; port has not been updated yet.</para>
+
+    <para>The second catch is that &os;'s bug tracking system sorts
+      problem reports according to the category the originator
+      selected.  Therefore, if you select the wrong category when you
+      submit your problem report, there is a good chance that it will
+      go unnoticed for a while, until someone re-categorizes it.</para>
+
     <para>Then you should ascertain whether or not the problem is
       timely.  There are few things
       that will annoy a developer more than receiving a problem report
@@ -224,25 +243,6 @@
 	  are also available via CVSweb.</para>
       </listitem>
     </itemizedlist>
-
-    <para>Next, you need to make sure your problem report goes to the
-      right people.</para>
-
-    <para>The first catch here is that if the problem is a bug in
-      third-party software (a port or a package you have installed), you
-      should report the bug to the original author, not to the &os;
-      Project.  There are two exceptions to this rule: the first is if
-      the bug does not occur on other platforms, in which case the
-      problem may lie in how the software was ported to &os;; the
-      second is if the original author has already fixed the bug and
-      released a patch or a new version of his software, and the
-      &os; port has not been updated yet.</para>
-
-    <para>The second catch is that &os;'s bug tracking system sorts
-      problem reports according to the category the originator
-      selected.  Therefore, if you select the wrong category when you
-      submit your problem report, there is a good chance that it will
-      go unnoticed for a while, until someone re-categorizes it.</para>
   </section>
 
   <section id="pr-writing">