about summary refs log tree commit diff
path: root/src
diff options
context:
space:
mode:
authorGeoff Catlin <gcatlin@gmail.com>2016-03-01 08:42:34 -0500
committerGeoff Catlin <gcatlin@gmail.com>2016-03-01 08:42:34 -0500
commitdcb92abbe1ca08ce3d6124e6a51111e534d7d281 (patch)
tree7c9e27a3daef443955147c149b196c603ce9a0fe /src
parent0a52494f7e259f49a3be176dc6fb151c755d6686 (diff)
downloadrust-dcb92abbe1ca08ce3d6124e6a51111e534d7d281.tar.gz
rust-dcb92abbe1ca08ce3d6124e6a51111e534d7d281.zip
grammar: 'fewer' instead of 'less'
Diffstat (limited to 'src')
-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