diff --git a/README.md b/README.md
index e680e1e..0b0c1f0 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ If you are not sure if a change requires a Change Proposal, just ask on the appr
 2. New change proposals will be reviewed by the relevant Team Leads for completeness, understandability of proposal, and to determine what team(s) is best suited to discuss this proposal. 
      * The Steering Committee will ensure that all relevant Team Leads are aware of new change proposals which have implications for more than one Team 
 3. The relevant Team Leads will make reasonable efforts to facilitate a decision as to whether a properly completed proposal is accepted to move forward or not within two months. If Owners fail to provide any needed further input or responses, a Change Proposal issue may be closed without decision. 
-     * If a proposal is to move forward, this will be noted in the issue and further discussion and related tasks will move to the appropriate SPDX repo or other forum, as applicable, and noted in the original change proposal issue.
+     * If a proposal is to move forward, this will be noted in the issue and further discussion and related tasks will move to the appropriate SPDX repo or other forum, as applicable, and noted in the original change proposal issue and the issue here will be closed.
      * If a proposal is not to move forward, this will be noted in the change proposal and the issue will be closed.
 4. For accepted proposals, further discussion will occur in the appropriate SPDX repo or other form. Owners of change proposals should ensure they are aware of this and have joined Team mailing lists, are available to join calls, follow Github repos, etc.
      * If Owners fail to participate in discussions, a Change Proposal may be closed without implementation at the discretion of the applicable Team Leads.