Index: site-author/incubation/Process_Description.xml
===================================================================
--- site-author/incubation/Process_Description.xml	(revision 505776)
+++ site-author/incubation/Process_Description.xml	(working copy)
@@ -144,10 +144,10 @@
 
           <strong>Incubator PMC
 </strong>(referencing the voting result e-mail) that your candidate project be
-escalated to
+accepted by the Incubator as a
 
           <strong>Podling
-</strong>status. The Sponsor will assign a
+</strong>. The Sponsor will assign a
 
           <strong>Mentor
 </strong>. The Mentor may, or may not, be your original Champion. If not, it
@@ -190,7 +190,7 @@
 (infrastructure, communications, decision making) you will inevitably
 come under an assessment by the Incubator PMC concerning the exit of
 your project from the incubator. Keep in mind that exit can be a good
-things and bad thing. Exit via escalation to a top-level project or
+thing and bad thing. Exit via graduation to a top-level project or
 perhaps a subproject of an existing PMC would typically be viewed as
 a positive exit. On the other-hand, termination is also an exit
 condition that may be considered. With an upcoming assessment it is
@@ -208,7 +208,7 @@
 </li>
           <li>continuation under incubation with recommendations; or
 </li>
-          <li>exit via escalation into Apache.
+          <li>graduation into Apache.
 </li>
         </ul>
         <p>Note that whilst this is a recommendation, it carries a lot of
@@ -252,8 +252,8 @@
 arise.
 </p>
       </section>
-      <section id="Escalation">
-        <title>Escalation
+      <section id="Graduaion">
+        <title>Graduaion
 </title>
         <p>For Podlings that aim to establish sub-projects or products within
 existing communities you are almost home-free. The main issues you
Index: site-author/incubation/Incubation_Policy.xml
===================================================================
--- site-author/incubation/Incubation_Policy.xml	(revision 505783)
+++ site-author/incubation/Incubation_Policy.xml	(working copy)
@@ -362,18 +362,18 @@
 </p>
         <p>After each review, the Incubator PMC SHALL produce an Assessment of
 the project. The Assessment SHALL contain one of three
-recommendations :
+recommendations:
 </p>
         <ul>
           <li>that the Podling be Terminated;
 </li>
           <li>that the Podling continue in Incubation; or
 </li>
-          <li>that the Podling be escalated out of the Incubator.
+          <li>that the Podling be Graduated from Incubation.
 </li>
         </ul>
-        <p>Termination and Escalation are discussed in more detail in section
-"Exiting the Incubator".
+        <p>Termination and Graduation are discussed in more detail in section
+"Graduating from the Incubator".
 </p>
       </section>
       <section id="Disputing+an+Assessment">
@@ -389,7 +389,7 @@
 feedback MAY include a change to the original Assessment.
 </p>
         <p>Should the Podling and/or Mentor still disagree with the contents of
-the report, they may appeal to the Board of the Apache Software
+the report, they MAY appeal to the Board of the Apache Software
 Foundation. Such an appeal MUST include
 </p>
         <ul>
@@ -503,16 +503,16 @@
         </section>
       </section>
     </section>
-    <section id="Exiting+the+Incubator">
-      <title>Exiting the Incubator
+    <section id="Graduating+from+the+Incubator">
+      <title>Graduating from the Incubator
 </title>
-      <p>This section describes the requirements and process for exiting the
+      <p>This section describes the requirements and process for graduating from the
 Incubator.
 </p>
-      <section id="Minimum+Exit+Requirements">
-        <title>Minimum Exit Requirements
+      <section id="Minimum+Graduation+Requirements">
+        <title>Minimum Graduation Requirements
 </title>
-        <p>Prior to escalation to the ASF, a Podling needs to show that :
+        <p>Prior to graduation, a Podling needs to show that :
 </p>
         <ul>
           <li>it is a worthy and healthy project;
@@ -522,18 +522,18 @@
           <li>it "gets" the Apache Way.
 </li>
         </ul>
-        <p>This is achieved by imposing a set of Exit Criteria that, when met,
+        <p>This is achieved by imposing a set of Graduation Criteria that, when met,
 will demonstrate these objectives.
 </p>
-        <p>Therefore, to successfully exit the Incubator and be escalated fully
-into the ASF, a Podling SHALL meet the minimum exit requirements
+        <p>Therefore, to successfully graduate from the Incubator
+into the ASF, a Podling SHALL meet the minimum requirements
 detailed below. The Incubator PMC MAY set additional requirements at
 their discretion. Such additional requirements MAY be proposed by the
 Mentor or the Sponsor, however only the Incubator PMC is authorised
 to formally place such requirements on a Podling.
 </p>
         <p>The minimum requirements that a Podling SHALL meet prior to being
-successfully escalated to the ASF are :
+graduated to the ASF are :
 </p>
         <ul>
           <li>
@@ -660,23 +660,23 @@
 such, an appeal is unlikely to be successful.
 </p>
       </section>
-      <section id="Migration+as+a+Top+Level+Project">
-        <title>Migration as a Top Level Project
+      <section id="Graduation+as+a+Top+Level+Project">
+        <title>Graduation as a Top Level Project
 </title>
         <p>In cases where a Podling has successfully completed Incubation, and
-is exiting the Incubator to become a Top Level Project, the Incubator
+is graduating from the Incubator to become a Top Level Project, the Incubator
 PMC SHALL provide a recommendation to the board that the Podling is
-ready to escalate. The recommendation SHALL include a draft
+ready to gradualate. The recommendation SHALL include a draft
 resolution for the board to vote on.
 </p>
       </section>
-      <section id="Migration+as+a+sub-project">
-        <title>Migration as a sub-project
+      <section id="Graduation+as+a+sub-project">
+        <title>Graduation as a sub-project
 </title>
         <p>In cases where a Podling has successfully completed Incubation, and
-is exiting the Incubator to become a sub-project within an already
+is graduating from the Incubator to become a sub-project within an already
 existing Top Level Project, the Incubator PMC SHALL provide a
-recommendation to the TLP that the Podling is ready to escalate.
+recommendation to the TLP that the Podling is ready to graduate.
 </p>
       </section>
       <section id="Post-Graduation+Check+List">
@@ -697,11 +697,11 @@
 
         </p>
         <ul>
-          <li>Move svn repository from incubator to new location
+          <li>Migrate svn repository from incubator to its new location
 
             <ul>
               <li>PMC sends email to infrastructure@ and opens a JIRA issue requesting
-that infrastructure move the svn repository.
+that infrastructure migrate the svn repository.
 </li>
               <li>PMC updates the svn-authorization files to provide committers access
 to the newly-named repositories.
@@ -712,7 +712,7 @@
 </li>
             </ul>
           </li>
-          <li>Move web site
+          <li>Migrate web site
 
             <ul>
               <li>PMC emails root@ and opens a JIRA issue requesting UNIX karma for
@@ -750,11 +750,11 @@
 </li>
             </ul>
           </li>
-          <li>Move mail lists:
+          <li>Migrate mail lists:
 
             <ul>
               <li>PMC sends email to infrastructure@ and opens a JIRA issue requesting
-that the mailing lists and archives be moved.
+that the mailing lists and archives be migrated
 </li>
             </ul>
           </li>
Index: site-author/incubation/Roles_and_Responsibilities.xml
===================================================================
--- site-author/incubation/Roles_and_Responsibilities.xml	(revision 505776)
+++ site-author/incubation/Roles_and_Responsibilities.xml	(working copy)
@@ -58,7 +58,7 @@
 </li>
           <li style="list-style: none">
             <ul>
-              <li>successfully exit incubation;
+              <li>graduate from incubation;
 </li>
               <li>continue to receive guidance and support within the Incubator; or
 </li>
@@ -120,7 +120,7 @@
 or planned with existing Apache Projects/Products).
 </li>
         </ul>
-        <p>Naturally, projects will need more than this in order to exit
+        <p>Naturally, projects will need more than this in order to graduate from
 incubation status.
 </p>
         <p>A candidate project compliant with the above criteria may be proposed
Index: site-publish/incubation/Roles_and_Responsibilities.html
===================================================================
--- site-publish/incubation/Roles_and_Responsibilities.html	(revision 505776)
+++ site-publish/incubation/Roles_and_Responsibilities.html	(working copy)
@@ -120,7 +120,7 @@
 </li>
           <li style="list-style: none">
             <ul>
-              <li>successfully exit incubation;
+              <li>graduate from incubation;
 </li>
               <li>continue to receive guidance and support within the Incubator; or
 </li>
@@ -186,7 +186,7 @@
 or planned with existing Apache Projects/Products).
 </li>
         </ul>
-<p>Naturally, projects will need more than this in order to exit
+<p>Naturally, projects will need more than this in order to graduate from
 incubation status.
 </p>
 <p>A candidate project compliant with the above criteria may be proposed
Index: site-publish/incubation/Process_Description.html
===================================================================
--- site-publish/incubation/Process_Description.html	(revision 505776)
+++ site-publish/incubation/Process_Description.html	(working copy)
@@ -208,10 +208,10 @@
 
           <strong>Incubator PMC
 </strong>(referencing the voting result e-mail) that your candidate project be
-escalated to
+accepted by the Incubator as a
 
           <strong>Podling
-</strong>status. The Sponsor will assign a
+</strong>. The Sponsor will assign a
 
           <strong>Mentor
 </strong>. The Mentor may, or may not, be your original Champion. If not, it
@@ -256,7 +256,7 @@
 (infrastructure, communications, decision making) you will inevitably
 come under an assessment by the Incubator PMC concerning the exit of
 your project from the incubator. Keep in mind that exit can be a good
-things and bad thing. Exit via escalation to a top-level project or
+things and bad thing. Exit via graduation to a top-level project or
 perhaps a subproject of an existing PMC would typically be viewed as
 a positive exit. On the other-hand, termination is also an exit
 condition that may be considered. With an upcoming assessment it is
@@ -274,7 +274,7 @@
 </li>
           <li>continuation under incubation with recommendations; or
 </li>
-          <li>exit via escalation into Apache.
+          <li>graduation into Apache.
 </li>
         </ul>
 <p>Note that whilst this is a recommendation, it carries a lot of
@@ -323,7 +323,7 @@
 </p>
 </div>
 <h3>
-   <a name="Escalation">Escalation
+   <a name="Graduaion">Graduaion
 </a>
 </h3>
 <div class="section-content">
Index: site-publish/incubation/Incubation_Policy.html
===================================================================
--- site-publish/incubation/Incubation_Policy.html	(revision 505783)
+++ site-publish/incubation/Incubation_Policy.html	(working copy)
@@ -450,18 +450,18 @@
 </p>
 <p>After each review, the Incubator PMC SHALL produce an Assessment of
 the project. The Assessment SHALL contain one of three
-recommendations :
+recommendations:
 </p>
 <ul>
           <li>that the Podling be Terminated;
 </li>
           <li>that the Podling continue in Incubation; or
 </li>
-          <li>that the Podling be escalated out of the Incubator.
+          <li>that the Podling be Graduated from Incubation.
 </li>
         </ul>
-<p>Termination and Escalation are discussed in more detail in section
-"Exiting the Incubator".
+<p>Termination and Graduation are discussed in more detail in section
+"Graduating from the Incubator".
 </p>
 </div>
 <h3>
@@ -479,7 +479,7 @@
 feedback MAY include a change to the original Assessment.
 </p>
 <p>Should the Podling and/or Mentor still disagree with the contents of
-the report, they may appeal to the Board of the Apache Software
+the report, they MAY appeal to the Board of the Apache Software
 Foundation. Such an appeal MUST include
 </p>
 <ul>
@@ -602,19 +602,19 @@
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />
-   <a name="Exiting+the+Incubator">Exiting the Incubator
+   <a name="Graduating+from+the+Incubator">Graduating from the Incubator
 </a>
 </h2>
 <div class="section-content">
-<p>This section describes the requirements and process for exiting the
+<p>This section describes the requirements and process for graduating from the
 Incubator.
 </p>
 <h3>
-   <a name="Minimum+Exit+Requirements">Minimum Exit Requirements
+   <a name="Minimum+Graduation+Requirements">Minimum Graduation Requirements
 </a>
 </h3>
 <div class="section-content">
-<p>Prior to escalation to the ASF, a Podling needs to show that :
+<p>Prior to graduation, a Podling needs to show that :
 </p>
 <ul>
           <li>it is a worthy and healthy project;
@@ -624,18 +624,18 @@
           <li>it "gets" the Apache Way.
 </li>
         </ul>
-<p>This is achieved by imposing a set of Exit Criteria that, when met,
+<p>This is achieved by imposing a set of Graduation Criteria that, when met,
 will demonstrate these objectives.
 </p>
-<p>Therefore, to successfully exit the Incubator and be escalated fully
-into the ASF, a Podling SHALL meet the minimum exit requirements
+<p>Therefore, to successfully graduate from the Incubator
+into the ASF, a Podling SHALL meet the minimum requirements
 detailed below. The Incubator PMC MAY set additional requirements at
 their discretion. Such additional requirements MAY be proposed by the
 Mentor or the Sponsor, however only the Incubator PMC is authorised
 to formally place such requirements on a Podling.
 </p>
 <p>The minimum requirements that a Podling SHALL meet prior to being
-successfully escalated to the ASF are :
+graduated to the ASF are :
 </p>
 <ul>
           <li>
@@ -765,26 +765,26 @@
 </p>
 </div>
 <h3>
-   <a name="Migration+as+a+Top+Level+Project">Migration as a Top Level Project
+   <a name="Graduation+as+a+Top+Level+Project">Graduation as a Top Level Project
 </a>
 </h3>
 <div class="section-content">
 <p>In cases where a Podling has successfully completed Incubation, and
-is exiting the Incubator to become a Top Level Project, the Incubator
+is graduating from the Incubator to become a Top Level Project, the Incubator
 PMC SHALL provide a recommendation to the board that the Podling is
-ready to escalate. The recommendation SHALL include a draft
+ready to gradualate. The recommendation SHALL include a draft
 resolution for the board to vote on.
 </p>
 </div>
 <h3>
-   <a name="Migration+as+a+sub-project">Migration as a sub-project
+   <a name="Graduation+as+a+sub-project">Graduation as a sub-project
 </a>
 </h3>
 <div class="section-content">
 <p>In cases where a Podling has successfully completed Incubation, and
-is exiting the Incubator to become a sub-project within an already
+is graduating from the Incubator to become a sub-project within an already
 existing Top Level Project, the Incubator PMC SHALL provide a
-recommendation to the TLP that the Podling is ready to escalate.
+recommendation to the TLP that the Podling is ready to graduate.
 </p>
 </div>
 <h3>
@@ -807,11 +807,11 @@
 
         </p>
 <ul>
-          <li>Move svn repository from incubator to new location
+          <li>Migrate svn repository from incubator to its new location
 
             <ul>
               <li>PMC sends email to infrastructure@ and opens a JIRA issue requesting
-that infrastructure move the svn repository.
+that infrastructure migrate the svn repository.
 </li>
               <li>PMC updates the svn-authorization files to provide committers access
 to the newly-named repositories.
@@ -822,7 +822,7 @@
 </li>
             </ul>
           </li>
-          <li>Move web site
+          <li>Migrate web site
 
             <ul>
               <li>PMC emails root@ and opens a JIRA issue requesting UNIX karma for
@@ -860,11 +860,11 @@
 </li>
             </ul>
           </li>
-          <li>Move mail lists:
+          <li>Migrate mail lists:
 
             <ul>
               <li>PMC sends email to infrastructure@ and opens a JIRA issue requesting
-that the mailing lists and archives be moved.
+that the mailing lists and archives be migrated
 </li>
             </ul>
           </li>