about summary refs log tree commit diff
path: root/src/doc/rustc-dev-guide
diff options
context:
space:
mode:
authorWho? Me?! <mark-i-m@users.noreply.github.com>2019-02-20 12:57:01 -0500
committerWho? Me?! <mark-i-m@users.noreply.github.com>2019-02-23 18:12:58 -0600
commit9bca4aa39b39cddfa829fce08131fb0b12bf6a7a (patch)
treec6d0e8afcc3ae35c5abf77b71f5bf7365661c172 /src/doc/rustc-dev-guide
parent2e90be41191918c59278448d123f43dee01eec8c (diff)
downloadrust-9bca4aa39b39cddfa829fce08131fb0b12bf6a7a.tar.gz
rust-9bca4aa39b39cddfa829fce08131fb0b12bf6a7a.zip
Update src/implementing_new_feature.md
Co-Authored-By: rajcspsg <raj.cs.psg@gmail.com>
Diffstat (limited to 'src/doc/rustc-dev-guide')
-rw-r--r--src/doc/rustc-dev-guide/src/implementing_new_feature.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/rustc-dev-guide/src/implementing_new_feature.md b/src/doc/rustc-dev-guide/src/implementing_new_feature.md
index 2bc65e145d6..d787954da34 100644
--- a/src/doc/rustc-dev-guide/src/implementing_new_feature.md
+++ b/src/doc/rustc-dev-guide/src/implementing_new_feature.md
@@ -78,7 +78,7 @@ For other features, you'll have to make a tracking issue for that feature. The i
 
 For tracking issues for features (as opposed to future-compat warnings), I don't think the description has to contain anything specific. Generally we put the list of items required for stabilization using a github list, e.g.
 
-```bash, ignore
+```txt
     **Steps:**
 
     - [ ] Implement the RFC (cc @rust-lang/compiler -- can anyone write up mentoring instructions?)
@@ -132,4 +132,4 @@ https://github.com/rust-lang/rust-forge/blob/master/rustc-bug-fix-procedure.md
 [value the stability of Rust]: https://github.com/rust-lang/rfcs/blob/master/text/1122-language-semver.md
 [stability in code]:
 [here]: https://rust-lang.github.io/rustc-guide/stabilization_guide.html
-[tracking issue]: 
\ No newline at end of file
+[tracking issue]: