Index: trunk/doc/devlog/20170213_edacore1.html
===================================================================
--- trunk/doc/devlog/20170213_edacore1.html	(revision 6901)
+++ trunk/doc/devlog/20170213_edacore1.html	(revision 6902)
@@ -88,8 +88,8 @@
 	     that can't be included in the same repository for whatever legal
 	     reasons. Yes, this excludes a lot of ISO and STEP and IPC stuff,
 	     and results in effort duplication while we design our own formats.
-	     But there's no point in making a compromise on this and building
-	     semi-free things then see some projects refusing to depend on it
+	     But there's no point in making a compromise on this and building on
+	     non-free things then see some projects refusing to depend on it
 	     because of the legal implications.
 </ul>
 
@@ -154,7 +154,11 @@
 	     once a few tools already have support for "edacore", this will
 	     automatically happen. Someone, or hopefully even multiple people will
 	     make their public services. Or people will just use github, torrent
-	     or whatever techniques.
+	     or whatever techniques. Of course we can also run
+	     <a href="20170213_edacore2.html"> our own repository service </a> but
+	     that should not be tied together with the "edacore" idea, it should just
+	     be one instance that happens to be maintained by the same people who
+	     made up the specs.
 	<li> "Fancy features". Provide the bare minimum. It's a tradeoff between
 	     the "works everywhere" vs. "looks perfect in all little details". If
 	     the user wants the former, an interchange format is for that; for the