Remove additional mention of disabling features

Author: rcvalle

src/doc/rustc/src/exploit-mitigations.md

@@ -23,14 +23,15 @@ Furthermore, the Rust code and documentation encourage creating safe
 abstractions over unsafe code. This can cause a false sense of security if
 unsafe code is not properly reviewed and tested.
 
-Unsafe Rust disables some of the features that provide memory and thread
-safety guarantees. This causes programs or libraries to be susceptible to
-memory corruption (CWE-119)[8] and concurrency issues (CWE-557)[9]. Modern C
-and C++ compilers provide exploit mitigations to increase the difficulty to
-exploit vulnerabilities resulting from these issues. Therefore, the Rust
-compiler must also support these exploit mitigations in order to mitigate
-vulnerabilities resulting from the use of Unsafe Rust. This chapter is going
-to document these exploit mitigations and how they apply to Rust.
+Unsafe Rust introduces features that do not provide the same memory and
+thread safety guarantees. This causes programs or libraries to be
+susceptible to memory corruption (CWE-119)[8] and concurrency issues
+(CWE-557)[9]. Modern C and C++ compilers provide exploit mitigations to
+increase the difficulty to exploit vulnerabilities resulting from these
+issues. Therefore, the Rust compiler must also support these exploit
+mitigations in order to mitigate vulnerabilities resulting from the use of
+Unsafe Rust. This chapter is going to document these exploit mitigations and
+how they apply to Rust.
 
 
 ## Exploit mitigations