From d59a2afe586f69a6cf2454a205303ee57378c016 Mon Sep 17 00:00:00 2001 From: king6cong Date: Sun, 22 Jan 2017 15:45:06 +0800 Subject: [PATCH] better comment wording --- src/librustc/ty/trait_def.rs | 2 +- src/librustc_driver/lib.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/librustc/ty/trait_def.rs b/src/librustc/ty/trait_def.rs index c6d862b23bd5e..1dc494ca277b3 100644 --- a/src/librustc/ty/trait_def.rs +++ b/src/librustc/ty/trait_def.rs @@ -26,7 +26,7 @@ pub struct TraitDef { /// If `true`, then this trait had the `#[rustc_paren_sugar]` /// attribute, indicating that it should be used with `Foo()` - /// sugar. This is a temporary thing -- eventually any trait wil + /// sugar. This is a temporary thing -- eventually any trait will /// be usable with the sugar (or without it). pub paren_sugar: bool, diff --git a/src/librustc_driver/lib.rs b/src/librustc_driver/lib.rs index 0ecd12b3a903a..ad2aefbb79539 100644 --- a/src/librustc_driver/lib.rs +++ b/src/librustc_driver/lib.rs @@ -904,7 +904,7 @@ fn print_flag_list(cmdline_opt: &str, /// should continue, returns a getopts::Matches object parsed from args, /// otherwise returns None. /// -/// The compiler's handling of options is a little complication as it ties into +/// The compiler's handling of options is a little complicated as it ties into /// our stability story, and it's even *more* complicated by historical /// accidents. The current intention of each compiler option is to have one of /// three modes: