Apply a bunch of nits (no significant changes)

Co-Authored-By: lzutao <[email protected]>
Co-Authored-By: Sébastien Duquette <[email protected]>
Co-Authored-By: Wesley Wiser <[email protected]>
Co-Authored-By: Kuba <[email protected]>

Author: 5 people

text/0000-roadmap-2020.md

@@ -13,7 +13,7 @@ to empower everyone to build reliable and efficient software.
 The roadmap takes the form of the following goals for the project:
 
 * Prepare for a possible Rust 2021 Edition
-* Followthrough on in-progress designs and efforts
+* Follow-through on in-progress designs and efforts
 * Improve project functioning and governance:
   * Improve visibility into the state of initiatives and design efforts
   * Increase mentoring, leadership, and organizational bandwidth
@@ -70,15 +70,15 @@ about goals and ongoing projects for 2020, either in the form of
 We have laid out three 'major goals' for Rust in 2020:
 
 * Prepare for a possible Rust 2021 Edition
-* Followthrough on in-progress designs and efforts
+* Follow-through on in-progress designs and efforts
 * Improve project functioning and governance:
   * Improve visibility into the state of initiatives and design efforts
   * Increase mentoring, leadership, and organizational bandwidth
   * Make design discussions more productive and less exhausting 
 
 ## Prepare for a Rust 2021 edition
 
-[Editions] were establshed as a means to help communicate the progress of
+[Editions] were established as a means to help communicate the progress of
 the Rust language and provide a rallying point for overarching pieces of work.
 One of our goals for this year should be plan out any changes that we
 wish to make as part of the next Rust edition. If we are to continue
@@ -126,7 +126,7 @@ any edition-related change would require appropriate tooling to help
 people transition their code, though the tooling might not be
 completed this year.
 
-## Followthrough with in-progress designs and efforts
+## Follow-through with in-progress designs and efforts
 
 > I work with Rust for several years. The language is great, the
 > tooling is superb, but I have one growing uneasy feeling too. There
@@ -184,7 +184,7 @@ active efforts and how can I help" to "what is the status of feature
 X". This is true both for folks who are deeply embedded in the Rust
 organization and for newcomers.
 
-There are many ways to improve visibiility, but the most basic step is
+There are many ways to improve visibility, but the most basic step is
 simply expending more effort on posting updates and documenting the
 status.  Things like the Inside Rust blog are helpful here, and we
 should look for other ways to incorporate lightweight status updates
@@ -211,7 +211,7 @@ Part of the problem here is money. One of the biggest challenges
 around organizational work is that it is quite demanding in terms of
 time. It requires availability. It is difficult to do in your spare
 time. Therefore, helping to ensure that it is easier for people to get
-paid for their work on Rust -- and especialy their **organizational**
+paid for their work on Rust -- and especially their **organizational**
 work -- is one way we might make progress here.
 
 However, it's worth emphasizing that this doesn't necessarily mean
@@ -227,7 +227,7 @@ As Parity put it in their #rust2020 post:
 > feature without any assurance that the approach taken would be
 > accepted.”
 >
-> -- [Benjamin Kampmann, speaking for Parity](https://www.parity.io/rust-/)
+> -- [Benjamin Kampmann, speaking for Parity](https://www.parity.io/rust-2020/)
 
 ### Make design discussions more productive and less exhausting
 
@@ -263,7 +263,7 @@ e.g., the survey, edition, and so forth -- so that they begin earlier
 in 2020, versus the timing from this year.
 
 * January
-  * Rust 2020 survey results published
+  * Rust 2019 survey results published
   * Roadmap RFC opened
 * February 
 * March
@@ -316,7 +316,7 @@ We chose to take this approach for a few reasons:
 However, there are some clear downsides. In particular, the goals we
 have chosen are not the sort of goal that one can "complete". Clearly,
 for example, the structure of the organization will always be open to
-improvement, and there will always be a need to followthrough on
+improvement, and there will always be a need to follow-through on
 goals.
 
 Our expectation is that, over the course of the year, we will relate
@@ -335,7 +335,7 @@ during the actual RFC discussion.*
 It seems likely that we will pursue creating a Rust foundation this
 year, perhaps along the lines that [nikomatsakis described in a recent
 blog post][bpf]. We opted not to include that as a "line item" in this
-RFC because we were generally trying to describe specific solutions,
+RFC because we were generally trying not to describe specific solutions,
 but more to describe the goals that we should be working towards. Any
 effort to create a foundation would fit well under "Improve project
 functioning and governance", however.
@@ -365,4 +365,3 @@ be figured out as the work proceeds, which doesn't really apply here.
 
 Not applicable.
 
-