Fix typos.

src/SUMMARY.md

@@ -109,7 +109,7 @@
     - [Behavior considered undefined](behavior-considered-undefined.md)
     - [Behavior not considered unsafe](behavior-not-considered-unsafe.md)
 
-- [Constant Evalutation](const_eval.md)
+- [Constant Evaluation](const_eval.md)
 
 [Appendix: Influences](influences.md)
 

src/attributes.md

@@ -372,7 +372,7 @@ certain tools.
 
 Currently `clippy` is the only available lint tool.
 
-They only get checked when the associated tool is active, so if you try to use an `allow` attribute for a nonexistant tool lint, the compiler will not warn about the nonexistant lint until you use the tool.
+They only get checked when the associated tool is active, so if you try to use an `allow` attribute for a nonexistent tool lint, the compiler will not warn about the nonexistent lint until you use the tool.
 
 Otherwise, they work just like regular lint attributes:
 

src/const_eval.md

@@ -45,7 +45,7 @@ to be ran.
 A _const context_ is one of the following:
 
 * [Array type length expressions]
-* Repeat expression length expessions
+* Repeat expression length expressions
 * The initializer of
   * [constants]
   * [statics]

src/expressions/block-expr.md

@@ -72,7 +72,7 @@ impl Struct {
 fn move_by_block_expression() {
     let s = Struct;
 
-    // Move the value out of `s` in the block expreesion.
+    // Move the value out of `s` in the block expression.
     (&{ s }).borrow_self();
 
     // Fails to execute because `s` is moved out of.

src/items/functions.md

@@ -140,7 +140,7 @@ implemented by executing an illegal instruction.
 ## Const functions
 
 Functions qualified with the `const` keyword are const functions. _Const
-funcions_  can be called from within [const contexts]. When called from a const
+functions_  can be called from within [const contexts]. When called from a const
 context, the function is interpreted by the compiler at compile time. The
 interpretation happens in the environment of the compilation target and not the
 host. So `usize` is `32` bits if you are compiling against a `32` bit system,
@@ -156,7 +156,7 @@ number generator as a const function. Calling a const function at compile-time
 will always yield the same result as calling it at runtime, even when called
 multiple times. There's one exception to this rule: if you are doing complex
 floating point operations in extreme situations, then you might get (very
-slightly) different results. It is adviseable to not make array lengths and enum
+slightly) different results. It is advisable to not make array lengths and enum
 discriminants depend on floating point computations.
 
 Exhaustive list of permitted structures in const functions:

src/items/modules.md

@@ -78,7 +78,7 @@ valid path. The names added by the [prelude] can be removed by placing the
 ## Attributes on Modules
 
 Modules, like all items, accept outer attributes. They also accept inner
-attibutes: either after `{` for a module with a body, or at the beginning of the
+attributes: either after `{` for a module with a body, or at the beginning of the
 source file, after the optional BOM and shebang.
 
 The built-in attributes that have meaning on a function are [`cfg`],