about summary refs log tree commit diff
diff options
context:
space:
mode:
authorYoungsuk Kim <joseph942010@gmail.com>2020-06-20 22:53:51 -0400
committerGitHub <noreply@github.com>2020-06-20 22:53:51 -0400
commit63740548aa8887c92d8976ccf478cfb0c44611a5 (patch)
treeda52adfe53ea32b52218ce7625c227ba7ff14df0
parent7058471adec80a2a1e6092443e08546768c9c894 (diff)
downloadrust-63740548aa8887c92d8976ccf478cfb0c44611a5.tar.gz
rust-63740548aa8887c92d8976ccf478cfb0c44611a5.zip
Fix typos in doc comments
This commit fixes typos in the doc comments of 'librustc_mir/monomorphize/collector.rs'
-rw-r--r--src/librustc_mir/monomorphize/collector.rs6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/librustc_mir/monomorphize/collector.rs b/src/librustc_mir/monomorphize/collector.rs
index 36f3947d830..448d8cdd6c6 100644
--- a/src/librustc_mir/monomorphize/collector.rs
+++ b/src/librustc_mir/monomorphize/collector.rs
@@ -1,7 +1,7 @@
 //! Mono Item Collection
 //! ====================
 //!
-//! This module is responsible for discovering all items that will contribute to
+//! This module is responsible for discovering all items that will contribute
 //! to code generation of the crate. The important part here is that it not only
 //! needs to find syntax-level items (functions, structs, etc) but also all
 //! their monomorphized instantiations. Every non-generic, non-const function
@@ -79,7 +79,7 @@
 //! function or method call (represented by a CALL terminator in MIR). But
 //! calls are not the only thing that might introduce a reference between two
 //! function mono items, and as we will see below, they are just a
-//! specialized of the form described next, and consequently will don't get any
+//! specialized of the form described next, and consequently will not get any
 //! special treatment in the algorithm.
 //!
 //! #### Taking a reference to a function or method
@@ -158,7 +158,7 @@
 //! - Eager mode is meant to be used in conjunction with incremental compilation
 //!   where a stable set of mono items is more important than a minimal
 //!   one. Thus, eager mode will instantiate drop-glue for every drop-able type
-//!   in the crate, even of no drop call for that type exists (yet). It will
+//!   in the crate, even if no drop call for that type exists (yet). It will
 //!   also instantiate default implementations of trait methods, something that
 //!   otherwise is only done on demand.
 //!