Some small fixes

src/name-resolution.md

@@ -13,7 +13,7 @@ resolve a name once, since no new names can be added. If we fail to resolve a
 name now, then it is a compiler error.
 
 Name resolution can be complex. There are a few different namespaces (e.g.
-macros, values, types, lifetimes), and names my be valid at different (nested)
+macros, values, types, lifetimes), and names may be valid at different (nested)
 scopes. Also, different types of names can fail to be resolved differently, and
 failures can happen differently at different scopes. For example, for a module
 scope, failure means no unexpanded macros and no unresolved glob imports in

src/parallel-rustc.md

@@ -18,7 +18,7 @@ There are a few basic ideas in this effort:
   thread-safe. A key strategy here has been converting interior-mutable
   data-structures (e.g. `Cell`) into their thread-safe siblings (e.g. `Mutex`).
 
-[`rayon`]: https://crates.io/rayon
+[`rayon`]: https://crates.io/crates/rayon
 
 As of this writing, much of this effort is on hold due to lack of manpower. We
 have a working prototype with promising performance gains in many cases.

src/queries/incremental-compilation-in-detail.md

@@ -507,7 +507,7 @@ session. The overhead of doing so is a few percent of total compilation time.
 Data structures used as query results could be factored in a way that removes
 edges from the dependency graph. Especially "span" information is very volatile,
 so including it in query result will increase the chance that that result won't
-be reusable. See https://github.com/rust-lang/rust/issues/47389 for more
+be reusable. See <https://github.com/rust-lang/rust/issues/47389> for more
 information.