Automatically merged updates to draft EIP(s) 1679, 233 (ethereum#2081)

Hi, I'm a bot! This change was automatically merged because:

 - It only modifies existing Draft or Last Call EIP(s)
 - The PR was approved or written by at least one author of each modified EIP
 - The build is passing

EIPS/eip-1679.md

@@ -26,6 +26,10 @@ This meta-EIP specifies the changes included in the Ethereum hardfork named Ista
 
 - TBD
 
+### Rejected EIPs
+
+- TBD
+
 ### Proposed EIPs
 
 - [EIP-615](https://eips.ethereum.org/EIPS/eip-615): Subroutines and Static Jumps for the EVM

EIPS/eip-233.md

@@ -41,7 +41,10 @@ Once a timeline with key dates is agreed upon for other crucial dates. The basic
 
 Anyone that wishes to propose a Core EIP for the hard fork should make a PR against the Meta EIP representing the hard fork. The EIP must be published as at least `Draft`. It enters the _Proposed EIPs_ section, along with at least one person who is a point of contact for wanting to include the EIP.
 
-Once the EIP has been accepted by Core Devs, the EIP should be moved to the _Accepted EIPs_ section. If the EIP has major client implementations and no security issues by the timeline date, it is scheduled for inclusion.
+EIPs can move states by discussion done on the "[All Core Devs Meetings](https://github.com/ethereum/pm/)":
+- If accepted for a hard fork, the EIP should be moved to the _Accepted EIPs_ section. If the EIP has major client implementations and no security issues by the timeline date, it is scheduled for inclusion.
+- If rejected from a hard fork, the EIP should be moved to the _Rejected EIPs_ section.
+- Once the EIPs in the _Accepted EIPs_ section have successfully launched on a testnet roll out, they are moved to the _Included EIPs_ section.
 
 ---
 
@@ -80,6 +83,10 @@ This meta-EIP specifies the changes included in the Ethereum hardfork named Ista
 
 - TBD
 
+### Rejected EIPs
+
+- TBD
+
 ### Proposed EIPs
 
 - TBD