Fixing some typos and last phrasing changes

1 files changed, 13 insertions, 11 deletions

diff --git a/content/blog/103_rust_2019.md b/content/blog/103_rust_2019.md
index cf243e5..3e3a3d3 100644
--- a/content/blog/103_rust_2019.md
+++ b/content/blog/103_rust_2019.md
@@ -70,19 +70,20 @@ unless you are working towards a *very* well defined spec!
 
 Having the same team be in charge of both the overall 
 vision for a system and it's implementation isn't a bad thing,
-**given that the system is small enough!**
+*given that the system is small enough!*
 
-Exactly this is where the concept of teams comes in.
+This is where teams come in!
 Splitting up the community into groups of people who work on the same stuff,
-in smaller numbers, so that collaboration on this scale becomes possible agian.
+in smaller numbers, so that collaboration on this scale becomes possible again.
 
-In a way, that was also the idea of the working groups for the Rust 2018 edition.
+In a way, the Rust 2018 working groups were inspired by the same idea.
 The difference between teams and working groups being,
 that the latter has a more loosely defined governance structure and allows people
 to join and collaborate easier and more quickly.
 There's less "established structure" in a working group.
-This is one of the reasons why I feel that the Rust project
-needs to expand on the idea of working groups, maybe even replacing some teams.
+These lower barriers are one of the reasons why I'm a huge fan of working groups,
+and feel like the Rust project should expand on them in the future.
+Maybe some teams could even be replaced.
 
 But that's not fundamentally the issue that the project is facing.
 
@@ -103,7 +104,7 @@ if we are ever to fix the way that we make decisions.
 But before I go into detail about what that means to _me_, specifically,
 I want to talk quickly about the core team.
 
-The core team is a medium sized group of veteran Rust developers,
+The core team is a medium sized group of Rust developers,
 who oversee large areas of the development of Rust.
 As the website puts it:
 
@@ -116,10 +117,10 @@ as well as communication among smaller teams.
 Unfortunately this hasn't seemed to be the case in the past
 and is something the core team should work on this year.
 
-I think this is a responsibly that should also not be taken lightly.
+Note that I think, that this is a responsibly that should also not be taken lightly.
 Most of the members of the core team are also active in other teams,
-sometimes even leading other teams.
-I feel that this has lead to the role of the core team being neglected.
+sometimes even leading them.
+I feel that this is one of the reasons why this role has been neglected.
 
 ## Solutions
 
@@ -138,7 +139,8 @@ contribution climate of the rust project significantly.
 
 Ultimately, we have a problem in how we communicate.
 The lines between *vision* and *implementation* get blurred too often.
-Not only in RFC discussions. Implementation specific bikesheds on github
+Not only in RFC discussions. 
+Implementation specific bikesheds on github
 often result in new rationale being pushed forward,
 that have nothing to do with the actual question at hand.
 And as such, people often talk past each other.