Be a bit more correct about segfault causality

Fixes #30819
2016-01-11 08:48:35 -05:00 · 2016-01-11 08:48:35 -05:00 · eb2343f25b
commit eb2343f25b
parent d228cd3964
1 changed files with 2 additions and 2 deletions
--- a/src/doc/book/unsafe.md
+++ b/src/doc/book/unsafe.md
@ -41,8 +41,8 @@ unsafe impl Scary for i32 {}
 ```

 It’s important to be able to explicitly delineate code that may have bugs that
-cause big problems. If a Rust program segfaults, you can be sure it’s somewhere
-in the sections marked `unsafe`.
+cause big problems. If a Rust program segfaults, you can be sure the cause is
+related to something marked `unsafe`.

 # What does ‘safe’ mean?