Apply suggestions from code review

Links and 'note's

Co-authored-by: Eric Huss <eric@huss.org>

Author: BatmanAoD

src/items/functions.md

@@ -222,9 +222,9 @@ implementation.
 | panic runtime  | ABI          | `panic`-unwind                        | Foreign unwind (unforced) |
 | -------------- | ------------ | ------------------------------------- | ----------------------- |
 | `panic=unwind` | `"C-unwind"` | unwind                                | unwind                  |
-| `panic=unwind` | `"C"`        | abort                                 | UB                      |
+| `panic=unwind` | `"C"`        | abort                                 | [Undefined Behavior]    |
 | `panic=abort`  | `"C-unwind"` | `panic!` aborts (no unwinding occurs) | abort                   |
-| `panic=abort`  | `"C"`        | `panic!` aborts (no unwinding occurs) | UB                      |
+| `panic=abort`  | `"C"`        | `panic!` aborts (no unwinding occurs) | [Undefined Behavior]    |
 
 > **Note**: The LLVM backend of the `rustc` implementation
 > aborts the process by executing an illegal instruction.

src/linkage.md

@@ -221,7 +221,7 @@ both of the following characteristics:
 
 `rustc` enforces this restriction at link-time. To guarantee that
 a library will be linkable regardless of the panic mode used at
-link-time, the `ffi_unwind_calls` may be used. The lint flags any
+link-time, the [`ffi_unwind_calls` lint] may be used. The lint flags any
 calls to `-unwind` foreign functions or function pointers.
 
 Note: Cargo will automatically unify all crates to use the same `panic`

src/panic.md

@@ -20,11 +20,11 @@ panic traverses Rust frames, live objects in those frames that [implement
 recovery does occur (for instance at a thread boundary), the objects will have
 been "cleaned up" just as if they had gone out of scope normally.
 
-> As long as this guarantee of resource-cleanup is preserved, "unwinding" may
+> **Note**: As long as this guarantee of resource-cleanup is preserved, "unwinding" may
 > be implemented without actually using the mechanism used by C++ for the
 > target platform.
 
-> 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).
@@ -34,7 +34,7 @@ been "cleaned up" just as if they had gone out of scope normally.
 The actual behavior and implementation of `panic!` is controlled by the _panic
 runtime_.
 
-> The Rust standard library provides two panic runtimes: `panic_unwind` (the
+> **Note**: The Rust standard library provides two panic runtimes: `panic_unwind` (the
 > default) and `panic_abort`, which immediately aborts the process (which is
 > non-recoverable).