about summary refs log tree commit diff
diff options
context:
space:
mode:
authorVallentin <vallentinsource@gmail.com>2019-05-30 21:09:46 +0200
committerWho? Me?! <mark-i-m@users.noreply.github.com>2019-06-02 19:24:11 -0500
commitddb5a4090c73b18d37c8eaf511ceb87578d40c42 (patch)
tree94a417d319365124238e76afcc03395c45dcf57d
parentb94b7a5e25510d502552994cee93733b3410b3bf (diff)
downloadrust-ddb5a4090c73b18d37c8eaf511ceb87578d40c42.tar.gz
rust-ddb5a4090c73b18d37c8eaf511ceb87578d40c42.zip
Fixed misspelling
-rw-r--r--src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md2
-rw-r--r--src/doc/rustc-dev-guide/src/queries/query-evaluation-model-in-detail.md2
-rw-r--r--src/doc/rustc-dev-guide/src/traits/slg.md2
3 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md b/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md
index d1530d6c090..043db2f5354 100644
--- a/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md
+++ b/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md
@@ -7,7 +7,7 @@ figuring out where moves occur and tracking those.
 ## Initialization and moves
 
 From a user's perspective, initialization -- giving a variable some
-value -- and moves -- transfering ownership to another place -- might
+value -- and moves -- transferring ownership to another place -- might
 seem like distinct topics. Indeed, our borrow checker error messages
 often talk about them differently. But **within the borrow checker**,
 they are not nearly as separate. Roughly speaking, the borrow checker
diff --git a/src/doc/rustc-dev-guide/src/queries/query-evaluation-model-in-detail.md b/src/doc/rustc-dev-guide/src/queries/query-evaluation-model-in-detail.md
index 47412acef7d..7772f36beaa 100644
--- a/src/doc/rustc-dev-guide/src/queries/query-evaluation-model-in-detail.md
+++ b/src/doc/rustc-dev-guide/src/queries/query-evaluation-model-in-detail.md
@@ -204,7 +204,7 @@ OK as long as the mutation is not observable. This is achieved by two things:
 This is not an ideal setup because of the manual intervention needed, so it
 should be used sparingly and only when it is well known which queries might
 access a given result. In practice, however, stealing has not turned out to be
-much of a maintainance burden.
+much of a maintenance burden.
 
 To summarize: "Steal queries" break some of the rules in a controlled way.
 There are checks in place that make sure that nothing can go silently wrong.
diff --git a/src/doc/rustc-dev-guide/src/traits/slg.md b/src/doc/rustc-dev-guide/src/traits/slg.md
index 98547575dc9..948d3fc8ab1 100644
--- a/src/doc/rustc-dev-guide/src/traits/slg.md
+++ b/src/doc/rustc-dev-guide/src/traits/slg.md
@@ -147,7 +147,7 @@ are both represented with an index.)
 
 For each strand, we also optionally store a *selected subgoal*. This
 is the subgoal after the turnstile (`:-`) that we are currently trying
-to prove in this strand. Initally, when a strand is first created,
+to prove in this strand. Initially, when a strand is first created,
 there is no selected subgoal.
 
 [`ExClause`]: https://rust-lang.github.io/chalk/doc/chalk_engine/struct.ExClause.html