some text improvements

Author: tshepang

src/doc/rustc-dev-guide/src/sanitizers.md

@@ -19,8 +19,10 @@ The rustc compiler contains support for following sanitizers:
 
 To enable a sanitizer compile with `-Z sanitizer=...` option, where value is one
 of `address`, `cfi`, `hwaddress`, `kcfi`, `leak`, `memory` or `thread`.
-For more details on how to use sanitizers please refer to the sanitizer flag in [the
-unstable book](https://doc.rust-lang.org/unstable-book/).
+For more details on how to use sanitizers,
+please refer to the sanitizer flag in [The Unstable Book].
+
+[The Unstable Book]: https://doc.rust-lang.org/unstable-book
 
 ## How are sanitizers implemented in rustc?
 
@@ -43,13 +45,13 @@ Highlight of the most important aspects of the implementation:
 *  During LLVM code generation, the functions intended for instrumentation are
    [marked][sanitizer-attribute] with appropriate LLVM attribute:
    `SanitizeAddress`, `SanitizeHWAddress`, `SanitizeMemory`, or `SanitizeThread`.
-   By default all functions are instrumented, but this
+   By default, all functions are instrumented, but this
    behaviour can be changed with `#[sanitize(xyz = "on|off|<other>")]`.
 
 *  The decision whether to perform instrumentation or not is possible only at a
    function granularity.
    In the cases were those decision differ between
-   functions it might be necessary to inhibit inlining, both at [MIR
+   functions, it might be necessary to inhibit inlining, both at [MIR
    level][inline-mir] and [LLVM level][inline-llvm].
 
 *  The LLVM IR generated by rustc is instrumented by [dedicated LLVM
@@ -59,8 +61,8 @@ Highlight of the most important aspects of the implementation:
 *  When producing an executable, the sanitizer specific runtime library is
    [linked in][sanitizer-link].
    The libraries are searched for in the target libdir.
-   First relative to the overridden system root and subsequently
-   relative to the default system root.
+   First, the search is relative to the overridden system root, and subsequently,
+   it is relative to the default system root.
    Fall-back to the default system root
    ensures that sanitizer runtimes remain available when using sysroot overrides
    constructed by cargo `-Z build-std` or xargo.
@@ -82,20 +84,20 @@ Sanitizers are validated by code generation tests in
 [`tests/ui/sanitizer/`][test-ui] directory.
 
 Testing sanitizer functionality requires the sanitizer runtimes (built when
-`sanitizer = true` in `bootstrap.toml`) and target providing support for particular sanitizer.
-When sanitizer is unsupported on given target, sanitizers tests will be ignored.
+`sanitizer = true` in `bootstrap.toml`) and target providing support for particular a sanitizer.
+When a sanitizer is unsupported on a given target, sanitizer tests will be ignored.
 This behaviour is controlled by compiletest `needs-sanitizer-*` directives.
 
 [test-cg]: https://github.com/rust-lang/rust/tree/HEAD/tests/codegen-llvm
 [test-ui]: https://github.com/rust-lang/rust/tree/HEAD/tests/ui/sanitizer
 
-## Enabling sanitizer on a new target
+## Enabling a sanitizer on a new target
 
 To enable a sanitizer on a new target which is already supported by LLVM:
 
 1. Include the sanitizer in the list of `supported_sanitizers` in [the target
    definition][target-definition].
-   `rustc --target .. -Zsanitizer=..` should now recognize sanitizer as supported.
+   `rustc --target .. -Zsanitizer=..` should now recognize the sanitizer as supported.
 2. [Build the runtime for the target and include it in the libdir.][sanitizer-targets]
 3. [Teach compiletest that your target now supports the sanitizer.][compiletest-definition]
    Tests marked with `needs-sanitizer-*` should now run on the target.