Updated To Final (#2449)

EIPS/eip-2387.md

@@ -4,7 +4,7 @@ title: "Hardfork Meta: Muir Glacier"
 author: James Hancock (@madeoftin)
 discussions-to: https://ethereum-magicians.org/t/hard-fork-to-address-the-ice-age-eip-2387
 type: Meta
-status: Last Call
+status: Final
 review-period-end: 2019-12-12
 created: 2019-11-22
 requires: 1679, 2384
@@ -50,7 +50,7 @@ I want to address the rationale for the intention of the Iceage and the implemen
  - Forces the community to come back into agreement repeatedly...and it gives whatever portion of the community that wants to a chance to fork off
  - Is a check for the Core Devs in the case that a decision is made to freeze the code base of clients without the blessing of the community.
 
-*Note: Neither of these effects the Freedom to Fork. They are meant to encourage core-devs and the community to upgrade along with the network and prevent the case where sleeper forks remain dormant only later to be resurrected. The requirement for an active fork is to change a client in a way to respond to the ice age. This is in fact what Ethereum Classic has done.
+*Note: None of these effects the Freedom to Fork. They are meant to encourage core-devs and the community to upgrade along with the network and prevent the case where sleeper forks remain dormant only later to be resurrected. The requirement for an active fork is to change a client in a way to respond to the ice age. This is in fact what Ethereum Classic has done.
 
 This is not meant to be exhaustive, but the ideas above capture much of what has been written on the original intentions and process of creating the fork. Any additions to this list that need to be made, I am happy to include. Regardless, to effectively implement an updated design for the ice age, all of the intentions need to be revisited and clarified as part of any updates. This clarification will give a clear expectation for the community and core developers moving forward.