Rework the FAQ text regarding "Redline" versions of the documents.
Change-Id: I1df2afd8932a394ab62a3607dcc79ffafbeb61d3
diff --git a/committer_process/re-sign/faq.html b/committer_process/re-sign/faq.html
index 6d59281..4fb61fe 100644
--- a/committer_process/re-sign/faq.html
+++ b/committer_process/re-sign/faq.html
@@ -24,9 +24,25 @@
</ol>
<h2 id="what-changes-were-made-to-the-agreements">What Changes were
made to the Agreements?</h2>
+<p>The changes to the Agreements are basically:</p>
+<ol>
+ <li>We added terms to explicitly allow code contributions to
+ Eclipse projects to be used as the basis for specifications. As you
+ may know, the Eclipse Foundation has created a new specification
+ process, largely motivated by the migration of the Java EE
+ specifications from Oracle's Java Community Process (JCP) to the
+ Eclipse Foundation.</li>
+ <li>We added terms to the committer agreements which embed what is
+ covered by the Eclipse Contributor Agreement (ECA). So now committers
+ only have to sign or be covered by one document. This reduces the
+ amount of paperwork required from committers, and eliminates the
+ requirement for employees of member companies with an MCCA to
+ individually sign an ECA.</li>
+</ol>
<p>The links below provide redlined PDFs showing the differences
between the previous version of the agreements, and the revisions
- announced on November 5, 2018.</p>
+ announced on November 5, 2018. We encourage you to review these with
+ your advisors.</p>
<ol>
<li><a
href="2018-09-26-final-eclipse-contributor-agreement-redline.pdf">Eclipse
