about summary refs log tree commit diff
diff options
context:
space:
mode:
authorPhilipp Hansch <dev@phansch.net>2018-09-20 06:58:07 +0200
committerPhilipp Hansch <dev@phansch.net>2018-09-20 06:58:07 +0200
commit2b57cec649013e5209d10c6b83ecc963b019c3e1 (patch)
treeecb359001121aea66600140c984896e49a9f47b1
parentf9511bfdc3753f22cfc33d53159bcd4226c307c2 (diff)
downloadrust-2b57cec649013e5209d10c6b83ecc963b019c3e1.tar.gz
rust-2b57cec649013e5209d10c6b83ecc963b019c3e1.zip
s/rustc/Rust/
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
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