Fix typos.

Author: waywardmonkeys

src/debugging-support-in-rustc.md

@@ -1,7 +1,7 @@
 # Debugging support in the Rust compiler
 
 This document explains the state of debugging tools support in the Rust compiler (rustc).
-The document gives an overview of debugging tools like GDB, LLDB etc. and infrastrcture
+The document gives an overview of debugging tools like GDB, LLDB etc. and infrastructure
 around Rust compiler to debug Rust code. If you want to learn how to debug the Rust compiler
 itself, then you must see [Debugging the Compiler] page.
 

src/kinds.md

@@ -15,7 +15,7 @@ For example, given a `HashMap<K, V>` with two type parameters, `K` and `V`, an
 instantiation of the parameters, for example `HashMap<i32, u32>`, would be
 represented by the substitution `&'tcx [tcx.types.i32, tcx.types.u32]`.
 
-`Subst` provides various convenience methods to instantiant substitutions
+`Subst` provides various convenience methods to instantiate substitutions
 given item definitions, which should generally be used rather than explicitly
 constructing such substitution slices.
 

src/miri.md

@@ -131,7 +131,7 @@ evaluation of another constant simply calls `tcx.const_eval`, which produces an
 entirely new and independent stack frame.
 
 The frames are just a `Vec<Frame>`, there's no way to actually refer to a
-`Frame`'s memory even if horrible shenigans are done via unsafe code. The only
+`Frame`'s memory even if horrible shenanigans are done via unsafe code. The only
 memory that can be referred to are `Allocation`s.
 
 Miri now calls the `step` method (in

src/stabilization_guide.md

@@ -34,8 +34,8 @@ Places that may need updated documentation:
     to the language, updating examples is important.
 - [Rust by Example]: As needed.
 
-Prepare PRs to update documentations invovling this new feature
-for  repositories mentioned above. Maintainers of these repositories
+Prepare PRs to update documentation involving this new feature
+for repositories mentioned above. Maintainers of these repositories
 will keep these PRs open until the whole stabilization process
 has completed. Meanwhile, we can proceed to the next step.
 
@@ -44,7 +44,7 @@ has completed. Meanwhile, we can proceed to the next step.
 Find the tracking issue of the feature, and create a short
 stabilization report. Essentially this would be a brief summary
 of the feature plus some links to test cases showing it works
-as expected, along with a list of edge cases that came up and
+as expected, along with a list of edge cases that came up
 and were considered. This is a minimal "due diligence" that
 we do before stabilizing.
 

src/ty.md

@@ -64,7 +64,7 @@ defining all of the different kinds of types in the compiler.
 > known later.).
 
 To allocate a new type, you can use the various `mk_` methods defined
-on the `tcx`. These have names that correpond mostly to the various kinds
+on the `tcx`. These have names that correspond mostly to the various kinds
 of type variants. For example:
 
 ```rust,ignore