Update 2019-10-30.md

Author: raullenchai

postmortem/2019-10-30.md

@@ -20,18 +20,20 @@ More than 1/3 delegates were not upgraded to 0.9.1 or 0.9.2 correctly:
 
 
 # Mitigation
-IoTeX Foundation outreached to these delegates and helped them to upgrade to 0.9.1/2; and the chain started to operate right after enough delegates come back online. Although there are stragllers still, the number of them is less than 1/3 of delegates. IoTeX Foundation will keep outreaching to the stragllers.
+IoTeX Foundation outreached to these delegates and helped them to upgrade to 0.9.1/2; and the chain started to operate right after enough delegates come back online. Although there are stragllers still, the number of them is less than 1/3 of delegates. IoTeX Foundation will keep outreaching to the stragllers. 
 
+After ~12 hours, all delegates have upgraded.
 
 # Next Steps
-## Short Term
-1. Make versions of nodes available on member.iotex.io 
-https://github.com/iotexproject/web-bp/issues/1391
-
-2. Tie config/genensis yaml versions with binary
-https://github.com/iotexproject/iotex-core/issues/1585
-
-## Middle Term
-1. Slashing of delegates who failed to produce blocks and so on. The design of slashing is in progress.
-2. The protocol rewards the first (perhaps) 24 delegates who upgrade first.
-
+**Better Communication With Delegates***
+Collect valid contact information from delegates.
+
+**Easier Upgrade***
+1. Tie config/genensis yaml versions with iotex-core binary - https://github.com/iotexproject/iotex-core/issues/1585
+2. Develope a cli tool to validate node status - https://github.com/iotexproject/iotex-core/issues/1590
+
+**Effective Governance***
+1. Make more status of nodes available on member.iotex.io - https://github.com/iotexproject/web-bp/issues/1391
+2. Slashing of delegates who failed to produce blocks (above a threshold) and so on. The design of slashing is in progress.
+3. The protocol rewards the first (perhaps) 24 delegates who upgrade.
+4. More decentralized and more delegates.