A HREF="mailto:maillist" -> A HREF="mailto:maillist@FreeBSD.org"

"phraze" -> <qoute>phraze</quote>

Reviewed by:	maintainer

1 files changed, 13 insertions, 12 deletions

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 805b8df008..2ed26e43ae 100644
--- a/en_US.ISO_8859-1/articles/committers-guide/article.sgml
+++ b/en_US.ISO_8859-1/articles/committers-guide/article.sgml
@@ -498,8 +498,8 @@
       or, upon repeated offense, permanent removal of commit privileges.
       Three or more members of core, or the Principal Architect and another
       member of core acting in unison, have the power to temporarily suspend
-      commit privileges until -core as a whole has the chance to review the
-      issue.  In cases of "emergency" (a committer doing damage to the
+      commit privileges until <literal>-core</literal> as a whole has the chance to review the
+      issue.  In cases of <quote>emergency</quote> (a committer doing damage to the
       repository), a temporary suspension may also be done by the repository
       meisters or any other member of core who may happen to be awake at the
       time.  Only core as a whole has the authority to suspend commit
@@ -602,7 +602,7 @@
 	    for documentation on this.  Where sections of code have several
 	    maintainers, commits to affected areas by one maintainer need to
 	    be reviewed by at least one other maintainer.  In cases where the
-	    "maintainer-ship" of something isn't clear, you can also look at
+	    <quote>maintainer-ship</quote> of something isn't clear, you can also look at
 	    the CVS logs for the file(s) in question and see if someone has
 	    been working recently or predominantly in that area.</para>
 
@@ -663,7 +663,7 @@
 	    The release engineer has the same authority over the -stable
 	    branch as outlined in rule #5.</para>
 	
-	  <para>This is another "don't argue about it" issue since it's the
+	  <para>This is another <quote>don't argue about it</quote> issue since it's the
 	    release engineer who is ultimately responsible (and gets beaten
 	    up) if a change turns out to be bad.  Please respect this and give
 	    the release engineer your full cooperation when it comes to the
@@ -748,7 +748,7 @@
 	    running that code.  If you have a change which also may break
 	    another architecture, be sure and test on all supported
 	    architectures.  Currently, this is only the x86 and the alpha so
-	    it's pretty easy to do.  If you need to test on the axp, your
+	    it's pretty easy to do.  If you need to test on the AXP, your
 	    account on <hostid role="fqdn">beast.FreeBSD.org</hostid> will let
 	    you compile and test alpha binaries/kernels/etc.  As other
 	    architectures are added to the FreeBSD supported platforms list,
@@ -766,7 +766,7 @@
 	also verify that your formatting directives are correct by running
 	<command>make lint</command>.</para>
 
-      <para>For all on-line manual pages, run 'manck' (from ports) over the
+      <para>For all on-line manual pages, run <command>manck</command> (from ports) over the
 	man page to verify the all of the cross references and file references
 	are correct and that the man page has all of the appropriate
 	<makevar>MLINK</makevar>s installed.</para>
@@ -1001,8 +1001,8 @@
 
 	  <answer>
 	    <para>The ports manager will send out warning messages to
-	      the <email>freebsd-ports</email> and
-	      <email>cvs-committers</email> mailing lists announcing
+	      the <email>freebsd-ports@FreeBSD.org</email> and
+	      <email>cvs-committers@FreeBSD.org</email> mailing lists announcing
 	      the start of the impending release, usually two or three
 	      weeks in advance.  The exact starting time will not be
 	      determined until a few days before the actual release.
@@ -1011,8 +1011,8 @@
 	      when exactly the release will be rolled.</para>
 
 	    <para>When the freeze starts, there will be another
-	      announcement to the <email>cvs-committers</email> list,
-	      of course.</para>
+	      announcement to the <email>cvs-committers@FreeBSD.org</email>
+              list, of course.</para>
 	  </answer>
 	</qandaentry>
 
@@ -1023,8 +1023,9 @@
 
 	  <answer>
 	    <para>A few hours after the release, the ports manager
-	      will send out a mail to the <email>freebsd-ports</email>
-	      and <email>cvs-committers</email> mailing lists
+	      will send out a mail to the
+              <email>freebsd-ports@FreeBSD.org</email> and
+              <email>cvs-committers@FreeBSD.org</email> mailing lists
 	      announcing the end of the ports freeze.  Note that the
 	      release being cut does not automatically end the freeze.
 	      We have to make sure there will not be any last minute