fix another link

Author: steveklabnik

_posts/2017-12-21-rust-in-2017.md

@@ -57,7 +57,7 @@ There’s not room in a single post to cover everything that happened, but we’
 ## Rust should provide easy access to high quality crates
 - Crates.io added [categories](https://crates.io/categories) this year, which aim to provide a crate organization structure targeted towards providing crates that are good for a particular purpose.
 - We had a [lively RFC discussion](https://github.com/rust-lang/rfcs/pull/1824) about the best way to order crates within categories and keywords, which included [a survey of how people evaluate crates](http://rust-lang.github.io/rfcs/1824-crates.io-default-ranking.html#appendix-user-research).
-- That discussion culminated in a decision to [order crates by the number of downloads in the last 90 days](https://github.com/rust-lang/crates.io/issues/704), and surfacing of more information for people to use when doing their evaluation.
+- That discussion culminated in a decision to [order crates by the number of downloads in the last 90 days](https://github.com/rust-lang/crates.io/issues/702), and surfacing of more information for people to use when doing their evaluation.
 - Some of the additional information now available for crate authors to display on crates.io includes badges for CI status, [maintenance status](https://github.com/rust-lang/crates.io/issues/704), [code coverage](https://github.com/rust-lang/crates.io/issues/706), [GitHub statistics](https://github.com/rust-lang/crates.io/issues/705).
 - Most importantly, [crates.io now displays a crate’s README on the crate page](https://github.com/rust-lang/crates.io/issues/81)! Crate authors are encouraged to use this capability to provide getting started documentation with a small example of what it looks like to use this crate, because good documentation and examples were among the most-mentioned positive signals that people take into account when evaluating crates.
 ## Rust should be well-equipped for writing robust servers