1.36.0: random -> uninitialized.

Author: Centril

posts/2019-07-04-Rust-1.36.0.md

@@ -81,8 +81,8 @@ One of the main uses of this function has been to lazily allocate arrays.
 However, [`mem::uninitialized`] is an incredibly dangerous operation that essentially
 cannot be used correctly as the Rust compiler assumes that values are properly initialized.
 For example, calling `mem::uninitialized::<bool>()` causes *instantaneous __undefined behavior__*
-as the random bits in memory could be something other than `0` (for `false`) and `1` (for `true`)
--- the only two allowed bit patterns for `bool`.
+as the uninitialized bits could be something other than `0` (for `false`)
+and `1` (for `true`) -- the only two allowed bit patterns for `bool`.
 
 To remedy this situation, in Rust 1.36.0, the type [`MaybeUninit<T>`] has been [stabilized][pr-60445].
 The Rust compiler will understand that it should not assume that a [`MaybeUninit<T>`] is a properly initialized `T`.