diff --git a/source/development_process.adoc b/source/development_process.adoc
index ff36418401e3095b949f07d0fef625488e981c33..e828e29611f911ee0ff1fd74f7748e3e4c5ee6f8 100644
--- a/source/development_process.adoc
+++ b/source/development_process.adoc
@@ -29,13 +29,15 @@ This document has the following sections:
 This document defines terms used elsewhere in Eclipse governance documents. In the event of any conflict between the terms set forth in this document and the terms of the xref:edp-documents[documents listed below], the terms of those documents shall take precedence.
 
 [[edp-documents]]
-=== 1.1 Applicable Governance Documents
+=== 1.1 Governance Documents
+
+All Committers and Project Leads engaged in Project activity are required to implement the policies and processes described by the https://www.eclipse.org/org/documents/[Eclipse Foundations Governance Documents], including:
 
-* {membershipAgreementUrl}[Eclipse Foundation Membership Agreement]
 * {bylawsUrl}[Eclipse Foundation Bylaws]
+* {membershipAgreementUrl}[Eclipse Foundation Membership Agreement]
 * {ipPolicyUrl}[Eclipse Foundation Intellectual Property Policy]
 * {securityPolicyUrl}[Eclipse Foundation Vulnerability Reporting Policy] 
-* {antitrustPolicyUrl}[Eclipse Foundation Anti-Trust Policy]
+* {antitrustPolicyUrl}[Eclipse Foundation Antitrust Policy]
 * {codeOfConductUrl}[Eclipse Foundation Community Code of Conduct]
 
 [[edp-terms]]
@@ -110,14 +112,18 @@ In practical terms, Projects are required to use resources and services approved
 [#3_Requirements]
 == 3. Requirements
 
-This document is entirely composed of requirements. In addition to the requirements specified in this development process, the EMO is instructed to clarify, expand, and extend this process by creating a set of development guidelines to advance the creation, evolution, promotion, and support of the open source Projects; and to cultivate both a community and an Ecosystem of complementary products and services.
+[#3_1_Requirements_and_Guidelines] This document is entirely composed of requirements. In addition to the requirements specified in this development process, the EMO is instructed to clarify, expand, and extend this process by creating a set of development guidelines to advance the creation, evolution, promotion, and support of the open source Projects; and to cultivate both a community and an Ecosystem of complementary products and services.
+
+[[edp-emo-responsibility]]
+=== 3.1 EMO Responsibility
+
+The EMO has the responsibility and authority to mitigate issues that arise when Committers fail to perform the required behaviors or engage in practices that risk reputational harm to the Eclipse Foundation and/or its Projects. This includes, but is not limited to, issues that arise due to a failure to implement the {securityPolicyUrl}[Eclipse Foundation Vulnerability Reporting Policy], the {ipPolicyUrl}[Eclipse Foundation Intellectual Property Policy], the {codeOfConductUrl}[Eclipse Foundation Community Code of Conduct], or other governance policies of the Eclipse Foundation.
 
-Projects that fail to perform the required behaviors will be terminated by the EMO.
+The EMO's authority includes, but is not limited to, the ability grant specific individuals equivalent to Committer privileges, add or remove Committers and Project Leads, suspend access to Project resources, and--in extreme cases--terminate the Project. 
 
 The EMO is not permitted to override or ignore the requirements listed in this document without the express written endorsement of the Board of Directors.
 
-[#3_1_Requirements_and_Guidelines]
-=== 3.1 [Reserved]
+The motivation for the EMO to take action along with description of the steps taken as part of the mitigation must be publicly disclosed within one week of action being taken. The xref:6_5_Grievance_Handling[Grievance Handling] section of this document describes the means by which a Member may respond in the event that they believe that the EMO has overstepped its authority.
 
 [#4_Structure_and_Organization]
 == 4. Project Structure and Organization
@@ -214,7 +220,7 @@ In the unlikely event that a member of the PMC becomes disruptive to the process
 
 Eclipse Projects are managed by one or more Project Leads. Project Leads are responsible for ensuring that their Project's Committers are following the Eclipse Foundation Development Process, and that the Project is engaging in the right sorts of activities to develop vibrant communities of users, Adopters, and Contributors. The initial Project Leads are appointed and approved in the Creation Review. Subsequently, additional Project Leads must be elected by the Project's Committers and approved by the Project's PMC and the EMO(ED).
 
-In the event that a Project Lead becomes disruptive to the process, is unwilling or unable to meet the obligations of the role, or ceases to contribute for an extended period, the individual may be retired from the role by the unanimous consent of the remaining Project Leads (if there are at least two other Project Leads), unanimous consent of the Project's PMC, or by direction of the EMO(ED).
+In the event that a Project Lead becomes disruptive to the process, is unwilling or unable to meet the obligations of the role, or ceases to contribute for an extended period, the individual may be retired from the role by the unanimous consent of the remaining Project Leads (if there are at least two other Project Leads), unanimous consent of the Project's PMC, or direction of the EMO(ED).
 
 [#4_7_Committers_and_Contributors]
 === 4.7 Committers and Contributors
@@ -225,7 +231,7 @@ Contributors who have the trust of the Project's Committers can, through electio
 
 The election process begins with an existing Committer on the same Project nominating the Contributor. The Project's Committers will vote for a period of no less than one week. If there are at least three (3) positive votes and no negative votes within the voting period, the Contributor is recommended to the Project's PMC for commit privileges. If there are three (3) or fewer Committers on the Project, a unanimous positive vote of all Committers is substituted. If the PMC approves, and the Contributor signs the appropriate Committer legal agreements established by the EMO (wherein, at the very least, the Developer agrees to abide by the Eclipse Intellectual Property Policy), the Contributor becomes a Committer and is given write access to the source code for that Project.
 
-At times, Committers may become inactive for a variety of reasons. The decision making process of the Project relies on active Committers who respond to discussions and vote in a constructive and timely manner. In the event that a Committer becomes disruptive to the process, is unwilling or unable to meet the obligations of the role, or ceases to contribute for an extended period, the individual may be retired from the role by the unanimous consent of the Project Leads, unanimous consent of the Project's PMC, or by direction of the EMO(ED). Unless otherwise specified, "an extended period" is defined as "no activity for more than six months".
+At times, Committers may become inactive for a variety of reasons. The decision making process of the Project relies on active Committers who respond to discussions and vote in a constructive and timely manner. In the event that a Committer becomes disruptive to the process, is unwilling or unable to meet the obligations of the role, or ceases to contribute for an extended period, the individual may be retired from the role by the unanimous consent of the Project Leads, unanimous consent of the Project's PMC, or direction of the EMO(ED). Unless otherwise specified, "an extended period" is defined as "no activity for more than six months".
 
 Active participation in the user communication channels and the appropriate Developer mailing lists is a responsibility of all Committers, and is critical to the success of the Project. Committers are required to monitor and contribute to the user communication channels.