From a5c7b96426cbddc1276ab4439ed2cc4a5689abc2 Mon Sep 17 00:00:00 2001
From: Ticki <@>
Date: Tue, 21 Jul 2015 21:36:29 +0200
Subject: [PATCH] Add info about usage of 'unsafe' keyword in bindings to
 foreign interfaces.

---
 src/doc/trpl/unsafe.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/src/doc/trpl/unsafe.md b/src/doc/trpl/unsafe.md
index 80b0c87473fa..897795e91533 100644
--- a/src/doc/trpl/unsafe.md
+++ b/src/doc/trpl/unsafe.md
@@ -100,10 +100,14 @@ that you normally can not do. Just three. Here they are:
 
 That’s it. It’s important that `unsafe` does not, for example, ‘turn off the
 borrow checker’. Adding `unsafe` to some random Rust code doesn’t change its
-semantics, it won’t just start accepting anything.
+semantics, it won’t just start accepting anything. But it will let you write
+things that _do_ break some of the rules.
 
-But it will let you write things that _do_ break some of the rules. Let’s go
-over these three abilities in order.
+You will also encounter the 'unsafe' keyword when writing bindings to foreign
+(non-Rust) interfaces. You're encouraged to write a safe, native Rust interface
+around the methods provided by the library.
+
+Let’s go over the basic three abilities listed, in order.
 
 ## Access or update a `static mut`