Style tweaks from code review

Co-authored-by: Travis Cross <[email protected]>

Author: BatmanAoD

src/behavior-considered-undefined.md

@@ -76,9 +76,9 @@ Please read the [Rustonomicon] before writing unsafe code.
   mechanisms outside Rust. Most assumptions of the Rust runtime are currently
   not explicitly documented.
   * For assumptions specifically related to unwinding, see [unwinding-ub].
-  * Deallocating a Rust stack frame without executing destructors for local
-    variables owned by the stack frame is always undefined. This can occur with
-    C functions like `longjmp`.
+  * The runtime assumes that a Rust stack frame is not deallocated without
+    executing destructors for local variables owned by the stack frame. This assumption
+    can be violated by C functions like `longjmp`.
 
 > **Note**: Undefined behavior affects the entire program. For example, calling
 > a function in C that exhibits undefined behavior of C means your entire

src/items/functions.md

@@ -244,13 +244,13 @@ from the "Native unwind" column in the table.
 | panic runtime  | ABI           | `panic`-unwind                        | Native unwind (unforced) |
 | -------------- | ------------  | ------------------------------------- | -----------------------  |
 | `panic=unwind` | unwinding     | unwind                                | unwind                   |
-| `panic=unwind` | non-unwinding | abort                                 | [Undefined Behavior]     |
+| `panic=unwind` | non-unwinding | abort                                 | [undefined behavior]     |
 | `panic=abort`  | unwinding     | `panic!` aborts (no unwinding occurs) | abort                    |
-| `panic=abort`  | non-unwinding | `panic!` aborts (no unwinding occurs) | [Undefined Behavior]     |
+| `panic=abort`  | non-unwinding | `panic!` aborts (no unwinding occurs) | [undefined behavior]     |
 
 [panic-modes]: ../panic.md#panic-runtimes
 [forced-unwinding]: https://rust-lang.github.io/rfcs/2945-c-unwind-abi.html#forced-unwinding
-[Undefined Behavior]: ../behavior-considered-undefined.md
+[undefined behavior]: ../behavior-considered-undefined.md
 
 ## Const functions
 

src/panic.md

@@ -11,7 +11,7 @@ over panic behavior:
   runtime.
 * [FFI ABIs](items/functions.md#unwinding) may alter how panics behave.
 
-> **Note**: The Standard Library provides the capability to explicitly panic
+> **Note**: The standard library provides the capability to explicitly panic
 > via the [`panic!` macro][macro-panic].
 
 ## Unwinding
@@ -31,7 +31,7 @@ if they had gone out of scope normally.
 > "unwinding" may be implemented without actually using the mechanism used by
 > C++ for the target platform.
 
-> **Note**: The Standard Library provides two mechanisms for recovering from a panic,
+> **Note**: The standard library provides two mechanisms for recovering from a panic,
 > [`catch_unwind`][fn-catch-unwind] (which enables recovery within the
 > panicking thread) and [`JoinHandle::join`][thread-join] (which enables a process to
 > continue execution without recovering the panicked thread).

src/runtime.md

@@ -47,7 +47,7 @@ fn panic(info: &PanicInfo) -> ! {
 
 The standard library provides an implementation of `panic_handler` that
 defaults to unwinding the stack but that can be [changed to abort the
-process][abort]. See also ["Panic runtimes"][panic-runtimes].
+process][abort]. See [panic runtimes] for more details.
 
 The standard library's panic behavior can be modified at runtime with the
 [`set_hook` function][set_hook].
@@ -82,7 +82,7 @@ display a console window on startup. It will run detached from any existing cons
 [abort]: ../book/ch09-01-unrecoverable-errors-with-panic.html
 [attribute]: attributes.md
 [crate types]: linkage.md
-[panic-runtimes]: panic.md#panic-runtimes
+[panic runtimes]: panic.md#panic-runtimes
 [set_hook]: std::panic::set_hook
 [static item]: items/static-items.md
 [subsystem]: https://msdn.microsoft.com/en-us/library/fcc1zstk.aspx