@@ -14,7 +14,7 @@ requiring a garbage collector or runtime, making it possible to
14
14
like to experiment with Rust, the
15
15
[ "Getting Started" section of the Rust book] [ book ] is your best bet
16
16
(if you prefer to use an e-reader, Pascal Hertleif maintains
17
- [ unofficial ebook vesions ] [ ebook ] as well).
17
+ [ unofficial e-book versions ] [ ebook ] as well).
18
18
19
19
What makes Rust different from other languages is its type system,
20
20
which represents a refinement and codification of "best practices"
@@ -31,8 +31,8 @@ The current Rust language is the result of a lot of iteration and
31
31
experimentation. The process has worked out well for us: Rust today is
32
32
both simpler and more powerful than we originally thought would be
33
33
possible. But all that experimentation also made it difficult to
34
- maintain a Rust project , since the language and standard library were
35
- constantly changing.
34
+ maintain projects written in Rust , since the language and standard
35
+ library were constantly changing.
36
36
37
37
** The 1.0 release marks the end of that churn.** This release is the
38
38
official beginning of our [ commitment to stability] [ stable ] , and as
@@ -42,17 +42,17 @@ of scope (some [caveats] apply, such as compiler bugs).
42
42
43
43
That said, releasing 1.0 doesn't mean that the Rust language is
44
44
"done". We have many [ improvements in store] [ priorities ] . In fact, the
45
- Nightly builds of Rust already demonstrates [ improvements to] [ 24965 ]
45
+ Nightly builds of Rust already demonstrate [ improvements to] [ 24965 ]
46
46
[ compile] [ 24615 ] [ times] [ 25323 ] (with more to come) and includes work
47
47
on new APIs and language features, like [ ` std::fs ` ] [ 1044 ] and
48
48
[ associated constants] [ 23606 ] .
49
49
50
50
To help ensure that compiler and language improvements make their way
51
51
out into the ecosystem at large as quickly as possible, we've adopted
52
52
a [ train-based] [ train ] release model. This means that we'll be issuing
53
- regular releases every six weeks, just like evergreen browsers. ** To
54
- kick off that process, we are also releasing Rust 1.1 beta today,
55
- simultaneously with Rust 1.0.**
53
+ regular releases every six weeks, just like the Firefox and Chrome web
54
+ browsers. ** To kick off that process, we are also releasing Rust 1.1
55
+ beta today, simultaneously with Rust 1.0.**
56
56
57
57
### Cargo and crates.io
58
58
@@ -80,7 +80,7 @@ Rust has been an open-source project from the start. Over the last few
80
80
years, we've been constantly looking for ways to make our governance
81
81
more open and community driven. Since we introduced the
82
82
[ RFC process] [ rfcs ] a little over a year ago, all major decisions
83
- about Rust are written up and discussed in the open in the form of a
83
+ about Rust are written up and discussed in the open in the form of an
84
84
RFC. Recently, we adopted a [ new governance model] [ 1068 ] , which
85
85
establishes a set of subteams, each responsible for RFCs in one
86
86
particular area. If you'd like help shape the future of Rust, we
0 commit comments