Updates following @xeno-by's comments

Author: propensive

blog/_posts/2018-02-14-tooling.md

@@ -17,11 +17,11 @@ tooling support some other languages enjoy.
 
 People care about language tools, and it says a lot for Scala that its success
 has come without ever having had the best tooling. But a better development
-experience in other languages has always made their grass seem greener, and
-over the years has undoubtedly limited the adoption of Scala.
+experience in other languages over the years has undoubtedly limited the
+adoption of Scala.
 
 Now, in 2018, there have been some developments primarily outside of the Scala
-community which present an new opportunity to change that.
+community which present a new opportunity to change that.
 
 ## The Language Server Protocol
 
@@ -42,8 +42,8 @@ With a many players from both commercial and open-source backgrounds already
 involved in tool development for Scala, we wanted to make sure that all the
 developers who had already contributed significantly to Scala's tooling could
 attend, but without having so many attendees as to make the meeting
-unmanageable. So we privately invited about fifty people, mostly suggested by
-the Advisory Board members.
+unmanageable. So we privately invited about fifty people suggested by the
+Advisory Board members, more than half of whom attended.
 
 This "closed doors" approach for the initial meeting was a practical
 compromise, made just for this one-off meeting. There are certainly other
@@ -68,8 +68,9 @@ framework in which decisions about the Scala LSP initiative could be made in
 future, in a way which the majority of people supported.
 
 During the meeting, we heard presentations on
-[Scalameta](http://scalameta.org/) and SemanticDB,
-[scalameta/language-server](https://github.com/scalameta/metals),
+[Scalameta](http://scalameta.org/) and
+[SemanticDB](https://github.com/scalameta/scalameta/blob/master/semanticdb/README.md),
+[Metals](https://github.com/scalameta/metals),
 [Bloop](https://github.com/scalacenter/bloop),
 [SBT](https://www.scala-sbt.org/),
 [Pants](https://www.pantsbuild.org/index.html), [Bazel](https://bazel.build/),
@@ -79,19 +80,20 @@ IDE](https://www.jetbrains.com/idea/), [Scala IDE](http://scala-ide.org/),
 and [TASTY](http://goo.gl/Mn6EhH).
 
 Another important premise for the meeting was that the tooling should be, as
-much as possible, compiler-agnostic. That is to say, we should need to use
+much as possible, compiler-agnostic. That is to say, we should not need to use
 a different protocol to work with Scala 2.11 or 2.12 or Dotty, and nor should
 users receive a different front-end experience for any Scala-like language.
 This support for other compilers is important for two reasons, even though the
 vast majority of current users run Scalac.
 
-Firstly, compilers like Dotty and [Rsc] want to hit the ground running with
-their tooling support; waiting another decade for a new tooling ecosystem to be
-invented is not an option.  When the time comes for Scala users to upgrade to
-Dotty, nobody wants the additional barrier of having to upgrade their build
-tool, documentation tools or IDE at the same time. They want a seamless
-transition. That's much easier to achieve by considering other compilers *now*
-than would be later.
+Firstly, compilers like Dotty and
+[Rsc](https://github.com/twitter/reasonable-scala) want to hit the ground
+running with their tooling support; waiting another decade for a new tooling
+ecosystem to be invented is not an option.  When the time comes for Scala users
+to upgrade to Dotty, nobody wants the additional barrier of having to upgrade
+their build tool, documentation tools or IDE at the same time. They want a
+seamless transition. That's much easier to achieve by considering other
+compilers *now* than would be later.
 
 The second reason is that there is a huge amount of excitement and enthusiasm
 around these new compilers, and we want to channel that into the Scala LSP
@@ -169,7 +171,7 @@ We will therefore take an imperfect but pragmatic approach and open voting only
 to those members of the Scala community who are willing to devote a small
 amount of their time to participating in a series of live votes, conducted
 online, which will take place on Wednesday, 28 February at 6pm GMT. Full
-details of the process will be published here, soon.
+details of the process will be published on this website, soon.
 
 I will be giving a keynote about the future of Scala Tooling at [Scala
 Sphere](http://scala.sphere.it/) in April, a large conference in Kraków