@@ -403,11 +403,10 @@ The CSS might be messed up, but you can verify that the HTML is right.
403
403
404
404
### Contributing to rustc-dev-guide
405
405
406
- Additionally, contributions to the [ rustc-dev-guide] [ rdg ] are always welcome.
407
- Contributions can be made directly at [ the rust-lang/rustc-dev-guide
408
- repo] [ rdgrepo ] . The issue tracker in that repo is also a great way to find
409
- things that need doing. There are issues for beginners and advanced compiler
410
- devs alike!
406
+ Contributions to the [ rustc-dev-guide] [ rdg ] are always welcome, and can be made directly at
407
+ [ the rust-lang/rustc-dev-guide repo] [ rdgrepo ] .
408
+ The issue tracker in that repo is also a great way to find things that need doing.
409
+ There are issues for beginners and advanced compiler devs alike!
411
410
412
411
Just a few things to keep in mind:
413
412
@@ -417,8 +416,8 @@ Just a few things to keep in mind:
417
416
Aim to provide a reasonable amount of context, possibly including but not limited to:
418
417
- A reason for why the data may be out of date other than "change", as change is a constant across
419
418
the project.
420
- - A date the comment was added, e.g. instead of writing _ "Currently, ..."_ , or
421
- _ "In the future, ..." _ , consider writing _ " As of January 2021, ..."_ .
419
+ - A date the comment was added, e.g. instead of writing _ "Currently, ..."_ consider writing
420
+ _ "As of January 2021, ..."_ .
422
421
Try to format the date as ` <MONTH> <YEAR> ` to ease search.
423
422
- A link to a relevant WG, tracking issue, ` rustc ` rustdoc page, or similar, that may provide
424
423
further explanation for the change process or a way to verify that the information is not
0 commit comments