better comment wording

diff --git a/src/librustc/ty/trait_def.rs b/src/librustc/ty/trait_def.rs
index c6d862b23bd5e393fc2bc67da607d37c730e7e7d..1dc494ca277b309e3ef0bb81f2f19688a9da2609 100644 (file)
--- 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 0ecd12b3a903aff65a8b4bc900039752ba57b84d..ad2aefbb79539c60b4ffa943ee4bc357142c4364 100644 (file)
--- a/src/librustc_driver/lib.rs
+++ b/src/librustc_driver/lib.rs
@@ -904,7 +904,7 @@ fn print_flag_list<T>(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: