Index: trunk/doc/devlog/20170212_ecosys.html
===================================================================
--- trunk/doc/devlog/20170212_ecosys.html	(revision 13646)
+++ trunk/doc/devlog/20170212_ecosys.html	(revision 13647)
@@ -75,10 +75,10 @@
 we potentially get a large collection of independent utilities. This sort
 of joins and pools developer resources too. At the end, the sum of all
 developers, users, experience, knowledge, data and code behind such an
-ecosystem. even with the overheads subtracted, can overweight of those
-behind centralized monolithic projects. <i>This is how it could compete with
-those - not on the level of individual tools, but on the level of the whole
-ecosystem.</i>
+ecosystem, even with the overheads subtracted, can overweight of those
+behind centralized monolithic projects. <i>This is how the ecosystem
+could compete with monoliths - not on the level of individual tools,
+but on the level of the whole ecosystem.</i>
 <p>
 There are well known examples of this setup. To list only two:
 <ul>
@@ -130,7 +130,7 @@
 <p>
 <b>Standardization:</b> e.g. standard, common file formats. Yes, life
 would be much easier if we had these already, but we can proceed without
-them. Let's waste some time today so we still have users by next week when
+them. Let's waste some time on code dups today so we still have users by next week when
 we can come up with the common file format multiple tools accept.
 <p>
 <b>Packaging:</b> we don't have to invent our own packaging and distribution