about summary refs log tree commit diff
path: root/src/doc
diff options
context:
space:
mode:
authorAlexander Regueiro <alexreg@me.com>2018-02-05 02:30:32 +0000
committerWho? Me?! <mark-i-m@users.noreply.github.com>2018-02-04 21:46:26 -0600
commitbe90a131125b18296853130d305d2e70c45b34a0 (patch)
treead50bed0ef18e916a1db988d19698c08404acc0f /src/doc
parent61450e53644df9c399b1bad076ac1d460946349e (diff)
downloadrust-be90a131125b18296853130d305d2e70c45b34a0.tar.gz
rust-be90a131125b18296853130d305d2e70c45b34a0.zip
More minor fixes.
Diffstat (limited to 'src/doc')
-rw-r--r--src/doc/rustc-dev-guide/src/hir.md4
-rw-r--r--src/doc/rustc-dev-guide/src/trait-resolution.md2
-rw-r--r--src/doc/rustc-dev-guide/src/ty.md4
3 files changed, 5 insertions, 5 deletions
diff --git a/src/doc/rustc-dev-guide/src/hir.md b/src/doc/rustc-dev-guide/src/hir.md
index d7eff5cd967..504f04b2408 100644
--- a/src/doc/rustc-dev-guide/src/hir.md
+++ b/src/doc/rustc-dev-guide/src/hir.md
@@ -23,9 +23,9 @@ functions, traits, impls, etc) in the HIR are not immediately
 accessible in the parents. So, for example, if there is a module item
 `foo` containing a function `bar()`:
 
-```
+```rust
 mod foo {
-  fn bar() { }
+    fn bar() { }
 }
 ```
 
diff --git a/src/doc/rustc-dev-guide/src/trait-resolution.md b/src/doc/rustc-dev-guide/src/trait-resolution.md
index 1c7f09e9be7..f12ce3b4b15 100644
--- a/src/doc/rustc-dev-guide/src/trait-resolution.md
+++ b/src/doc/rustc-dev-guide/src/trait-resolution.md
@@ -457,7 +457,7 @@ and the graph is consulted when propagating defaults down the
 specialization hierarchy.
 
 You might expect that the specialization graph would be used during
-selection – i.e., when actually performing specialization. This is
+selection – i.e. when actually performing specialization. This is
 not done for two reasons:
 
 - It's merely an optimization: given a set of candidates that apply,
diff --git a/src/doc/rustc-dev-guide/src/ty.md b/src/doc/rustc-dev-guide/src/ty.md
index 1da70d916f7..26b8c1ca8ff 100644
--- a/src/doc/rustc-dev-guide/src/ty.md
+++ b/src/doc/rustc-dev-guide/src/ty.md
@@ -142,7 +142,7 @@ structures that you can allocate, and which are found in this
 module. Here are a few examples:
 
 - `Substs`, allocated with `mk_substs` – this will intern a slice of types, often used to
-  specify the values to be substituted for generics (e.g., `HashMap<i32, u32>`
+  specify the values to be substituted for generics (e.g. `HashMap<i32, u32>`
   would be represented as a slice `&'tcx [tcx.types.i32, tcx.types.u32]`).
 - `TraitRef`, typically passed by value – a **trait reference**
   consists of a reference to a trait along with its various type
@@ -161,5 +161,5 @@ use ty::{self, Ty, TyCtxt};
 
 In particular, since they are so common, the `Ty` and `TyCtxt` types
 are imported directly. Other types are often referenced with an
-explicit `ty::` prefix (e.g., `ty::TraitRef<'tcx>`). But some modules
+explicit `ty::` prefix (e.g. `ty::TraitRef<'tcx>`). But some modules
 choose to import a larger or smaller set of names explicitly.