about summary refs log tree commit diff
path: root/src/doc
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2016-03-01 13:39:42 -0500
committerSteve Klabnik <steve@steveklabnik.com>2016-03-01 13:39:42 -0500
commit0ee1b992883c2b3b30091bb5266cafa004cb00b9 (patch)
treea2b3e0973b93e4de6dc5e7d37ee51b7011112915 /src/doc
parentc98c1b777fbe1a0c5ed74cd3de5a6b890da82974 (diff)
parentdcb92abbe1ca08ce3d6124e6a51111e534d7d281 (diff)
Rollup merge of #31987 - gcatlin:patch-1, r=steveklabnik
r? @steveklabnik
Diffstat (limited to 'src/doc')
-rw-r--r--src/doc/book/unsafe.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/book/unsafe.md b/src/doc/book/unsafe.md
index ecd196a9f0d..af4e351569f 100644
--- a/src/doc/book/unsafe.md
+++ b/src/doc/book/unsafe.md
@@ -4,7 +4,7 @@ Rust’s main draw is its powerful static guarantees about behavior. But safety
 checks are conservative by nature: there are some programs that are actually
 safe, but the compiler is not able to verify this is true. To write these kinds
 of programs, we need to tell the compiler to relax its restrictions a bit. For
-this, Rust has a keyword, `unsafe`. Code using `unsafe` has less restrictions
+this, Rust has a keyword, `unsafe`. Code using `unsafe` has fewer restrictions
 than normal code does.
 
 Let’s go over the syntax, and then we’ll talk semantics. `unsafe` is used in