diff options
| author | Katharina Fey <kookie@spacekookie.de> | 2019-11-03 23:29:56 +0100 |
|---|---|---|
| committer | Katharina Fey <kookie@spacekookie.de> | 2019-11-03 23:29:56 +0100 |
| commit | a877669256f0ad47184ae212ded6ab62575890eb (patch) | |
| tree | b8f51dcc8a1a95200a8a729159892b7ede509cc9 | |
| parent | ee013ce3bd099273a5f8e96075a2a1f6db21198a (diff) | |
Fixing a small typo
| -rw-r--r-- | content/blog/111_rust_2020.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/blog/111_rust_2020.md b/content/blog/111_rust_2020.md index c8591fd..e2b8645 100644 --- a/content/blog/111_rust_2020.md +++ b/content/blog/111_rust_2020.md @@ -26,7 +26,7 @@ changes. The idea is that a written proposal outlines a change's scope, implementation details, rationale and impact on the ecosystem, then people make comments on the proposal. Usually by the time that everybody has stopped shouting at each other, the RFC is ready to be -merged, meaning it is accepted and it's vision can be implemented. +merged, meaning it is accepted and its vision can be implemented. This can either be implementing a feature, or removing `unstable` flags from it. |