From eb2343f25b07dd1760d50546d7979a39c363ff09 Mon Sep 17 00:00:00 2001
From: Steve Klabnik <steve@steveklabnik.com>
Date: Mon, 11 Jan 2016 08:48:35 -0500
Subject: [PATCH] Be a bit more correct about segfault causality

Fixes #30819
---
 src/doc/book/unsafe.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/doc/book/unsafe.md b/src/doc/book/unsafe.md
index 1b223365bd63a..63e92316f370e 100644
--- 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?