Index: en_US.ISO8859-1/articles/problem-reports/article.xml
===================================================================
--- en_US.ISO8859-1/articles/problem-reports/article.xml
+++ en_US.ISO8859-1/articles/problem-reports/article.xml
@@ -101,30 +101,33 @@
       for an answer, consider posing the question to the
       &a.questions;.</para>
 
-    <para>Some cases where it may be appropriate to submit a problem
-      report about something that is not a bug are:</para>
+    <para>When submitting a PR about externally maintained software
+      (such as ports or software in the contrib/ directory) consider
+      the following:</para>
 
     <itemizedlist>
       <listitem>
-	<para>Notification of updates to externally maintained
-	  software (such as ports or software in the contrib/
-	  directory).</para>
-
 	<para>For unmaintained ports (<varname>MAINTAINER</varname>
-	  contains <literal>ports@FreeBSD.org</literal>), such update
-	  notifications might get picked up by an interested
+	  contains <literal>ports@FreeBSD.org</literal>),
+	  a PR about a new update 
+	  might get picked up by an interested
 	  committer, or you might be asked to provide a patch to
 	  update the port; providing it upfront will greatly improve
-	  your chances that the port will get updated in a timely
+	  the chances that the port will get updated in a timely
 	  manner.</para>
+      </listitem>
 
+      <listitem>
 	<para>If the port is maintained, PRs announcing new upstream
-	  releases are usually not very useful since they generate
+	  releases are usually not very helpfuk since they generate
 	  supplementary work for the committers, and the maintainer
-	  likely knows already there is a new version, they have
-	  probably worked with the developers on it, they are probably
-	  testing to see there is no regression, etc.</para>
+	  likely knows already there is a new version.  The &os;
+	  project uses <application>portscout</application> to
+	  automatically track when new versions of applications are
+	  released, and notify the maintainers automatically.</para>
+      </listitem>
 
+      <listitem>
 	<para>In either case, following the process described in <link
 	    xlink:href="&url.books.porters-handbook;/port-upgrading.html">Porter's
 	    Handbook</link> will yield the best results.  (You might