From 2b57cec649013e5209d10c6b83ecc963b019c3e1 Mon Sep 17 00:00:00 2001 From: Philipp Hansch Date: Thu, 20 Sep 2018 06:58:07 +0200 Subject: [PATCH] s/rustc/Rust/ --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 57260b17cf7..dda6ebb50d6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -211,7 +211,7 @@ You will then have to look for the last commit that contains `test-pass -> build The commit message contains a link to the PR. The PRs are usually small enough to discover the breaking API change and if they are bigger, they likely include some discussion that may help you to fix Clippy. -Fixing build failures caused by rustc updates, can also be a good way to learn about rustc internals. +Fixing build failures caused by Rust updates, can also be a good way to learn about Rust internals. If you decide to make Clippy work again with a Rust commit that breaks it, you probably want to install the latest Rust from master locally and run Clippy