Corrections needed for Bitshares blog

[cass]

https://github.com/bitshares/bitshares.github.io/pull/5

[mint chocolate chip]

https://github.com/bitshares/bitshares.github.io/blob/master/_posts/en/2015-09-11-BitShares-2.0-Launching-on-October-13th.md

ok mistake 1 + 2 located and updated ..

what do you think has to get updated on 3 +4 your mention ?

Remove the 'be have'

[cass]

https://github.com/bitshares/bitshares.github.io/blob/master/_posts/en/2015-09-11-BitShares-2.0-Launching-on-October-13th.md

ok mistake 1 + 2 located and updated ..

what do you think has to get updated on 3 +4 your mention ?

[cass]

good catch

[emailtooaj]

Hey guys,
I was reading the post at
https://bitshares.org/blog/2015/09/11/BitShares-2.0-Launching-on-October-13th/
and noticed some mistakes...

1. Postpone Bond Market
Back in June we announced on the forum the decision to postpone the Bond market features until after BitShares 2.0 was released. This decision was driven by an inability to fully test this feature and the belief that it was the most likely to need refinement, community feed back, and that it would woudl be unusable without a GUI.

5. Increased Block Interval to 3 seconds

Our goal of 1 second blocks has been postponed due to limitations in the P2P code we inhereted (inherited)from BTS 0.9. Initial tests showed on a global scale the latency would result in too many forks without developing a new P2P protocol. We have designed a new protocol that should be have dramatically lower latency. The witnesses/delegates can lower the block interval to 1 second without a hardfork as soon as they are confident that the network communication can operate reliably at 1hz(?) on a test network.