diff --git a/en_US.ISO8859-1/articles/committers-guide/article.sgml b/en_US.ISO8859-1/articles/committers-guide/article.sgml
index 0a1c88bf3c..cb8dc2fb14 100644
--- a/en_US.ISO8859-1/articles/committers-guide/article.sgml
+++ b/en_US.ISO8859-1/articles/committers-guide/article.sgml
@@ -171,6 +171,11 @@
       first test of your CVS skills.  If you can handle that one,
       you are probably going to be ok.</para>
 
+    <para>Your second commit should be to add an entry for yourself to
+      <filename>www/en/news/newsflash.sgml</filename>.  Look for the other
+      entries that look like <quote>A new committer</quote> and follow the
+      format.</para>
+
     <para>Your next step should be to introduce yourself to the other
       committers, otherwise no one will have any idea who you are or
       what you are working on.  You do not have to write a comprehensive
diff --git a/en_US.ISO_8859-1/articles/committers-guide/article.sgml b/en_US.ISO_8859-1/articles/committers-guide/article.sgml
index 0a1c88bf3c..cb8dc2fb14 100644
--- a/en_US.ISO_8859-1/articles/committers-guide/article.sgml
+++ b/en_US.ISO_8859-1/articles/committers-guide/article.sgml
@@ -171,6 +171,11 @@
       first test of your CVS skills.  If you can handle that one,
       you are probably going to be ok.</para>
 
+    <para>Your second commit should be to add an entry for yourself to
+      <filename>www/en/news/newsflash.sgml</filename>.  Look for the other
+      entries that look like <quote>A new committer</quote> and follow the
+      format.</para>
+
     <para>Your next step should be to introduce yourself to the other
       committers, otherwise no one will have any idea who you are or
       what you are working on.  You do not have to write a comprehensive