@@ -21,20 +21,20 @@ mechanics of contributing to [rust-lang/rust].
21
21
There are many ways to contribute to the success of Rust.
22
22
This guide focuses on a few avenues for the new contributor:
23
23
24
- * [ ** Finding, triaging and fixing issues** ] ( contribute-bugs.html ) . The
24
+ * [ Finding, triaging and fixing issues] ( contribute-bugs.html ) . The
25
25
basic work of maintaining a large and active project like Rust.
26
- * [ ** Documentation** ] ( contribute-docs.html ) . Not just official
26
+ * [ Documentation] ( contribute-docs.html ) . Not just official
27
27
documentation, but also for crates, blog posts, and other unofficial
28
28
sources.
29
- * [ ** Community building** ] ( contribute-community.html ) . Helping your fellow
29
+ * [ Community building] ( contribute-community.html ) . Helping your fellow
30
30
Rustacean, and expanding the reach of Rust.
31
- * [ ** Tooling, IDEs and infrastructure** ] ( contribute-tools.html ) . The
31
+ * [ Tooling, IDEs and infrastructure] ( contribute-tools.html ) . The
32
32
important pieces that make using a language practical and painless.
33
- * [ ** Libraries** ] ( contribute-libs.html ) . Rust's suitability for any
33
+ * [ Libraries] ( contribute-libs.html ) . Rust's suitability for any
34
34
particular task is mostly dependent on availability of quality
35
35
libraries.
36
- * [ ** Language, compiler and the standard
37
- library** ] ( contribute-compiler.html ) . Language design, feature
36
+ * [ Language, compiler and the standard
37
+ library] ( contribute-compiler.html ) . Language design, feature
38
38
implementation, performance improvement.
39
39
40
40
If you need additional guidance ask on [ #rust-internals] or
0 commit comments