svn commit: r44934 - head/en_US.ISO8859-1/articles/port-mentor-guidelines

[Benedict Reuschling]

Author: bcr
Date: Sat May 24 15:13:09 2014
New Revision: 44934
URL: http://svnweb.freebsd.org/changeset/doc/44934

Log:
  Remove contractions, capitalize titles and rephrase one sentence to avoid
  the use of "e.g.".

Modified:
  head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml

Modified: head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml	Sat May 24 15:05:41 2014	(r44933)
+++ head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml	Sat May 24 15:13:09 2014	(r44934)
@@ -26,7 +26,7 @@
   </info>
 
   <sect1 xml:id="port-mentor.guidelines">
-    <title>Guideline for Mentor/Mentee relationships</title>
+    <title>Guideline for Mentor/Mentee Relationships</title>
 
     <para>This section is intended to help demystify the
       mentoring process, as well as a way to openly promote a
@@ -38,7 +38,7 @@
       assurance of the product we call the Ports Tree.</para>
 
     <sect2 xml:id="why.mentor">
-      <title>Why mentor?</title>
+      <title>Why Mentor?</title>
 
       <itemizedlist>
 	<listitem>
@@ -130,20 +130,20 @@
 	  xlink:href="&url.articles.pr-guidelines;">PR handling
 	  guide</link>, and the <link
 	  xlink:href="&url.articles.committers-guide;">Committer's
-	  Guide</link>.  While it's not necessary to memorize all the
+	  Guide</link>.  While it is not necessary to memorize all the
 	details, every committer needs to have an overview of these
 	things to be an effective part of the community (and avoid as
 	many rookie mistakes as possible).</para>
     </sect2>
 
     <sect2 xml:id="mentees">
-      <title>Selecting a mentee</title>
+      <title>Selecting a Mentee</title>
 
       <para>There is no defined rule for what makes a candidate ready;
 	it can be a combination of number of PRs they have submitted
 	to <application>GNATS</application>, the number of ports
 	maintained, frequency of ports updates and/or level of
-	participation in a particular area of interest, e.g.
+	participation in a particular area of interest like
 	<application>GNOME</application>,
 	<application>KDE</application>,
 	<application>Gecko</application> or others.</para>
@@ -179,7 +179,7 @@
 
     </sect2>
     <sect2 xml:id="mentorship.duration">
-      <title>Mentorship duration</title>
+      <title>Mentorship Duration</title>
 
       <para>As the trust level develops and grows, the mentee may be
 	granted <quote>implicit</quote> commit rights.  This can
@@ -204,7 +204,7 @@
     </sect2>
 
     <sect2 xml:id="mentor.comentor.debate">
-      <title>Mentor/Co-Mentor debate</title>
+      <title>Mentor/Co-Mentor Debate</title>
 
       <para>When a request gets to portmgr, it usually reads as,
 	<quote>I propose 'foo' for a ports commit bit, I will
@@ -229,7 +229,7 @@
 
       <para>We expect mentees to be prepared for constructive
 	criticism from the community.  There's still a lot of
-	<quote>lore</quote> that isn't written down.  Responding well
+	<quote>lore</quote> that is not written down.  Responding well
 	to constructive criticism is what we hope we are selecting for
 	by first reviewing their existing contributions on IRC and
 	mailing lists.</para>