From 87bbb3c738e7d351d21fb19b51b2094b5afa0482 Mon Sep 17 00:00:00 2001 From: Wilfred Hughes Date: Sun, 29 Jan 2017 10:51:26 +0000 Subject: [PATCH] Minor grammar fix 'can not' -> 'cannot' The previous version suggested that the compiler chooses not to check, rather than being unable to check. --- src/doc/book/ffi.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/doc/book/ffi.md b/src/doc/book/ffi.md index 8ab580e6aa9..8d29f11aa05 100644 --- a/src/doc/book/ffi.md +++ b/src/doc/book/ffi.md @@ -56,9 +56,9 @@ almost any function that takes a pointer argument isn't valid for all possible inputs since the pointer could be dangling, and raw pointers fall outside of Rust's safe memory model. -When declaring the argument types to a foreign function, the Rust compiler can -not check if the declaration is correct, so specifying it correctly is part of -keeping the binding correct at runtime. +When declaring the argument types to a foreign function, the Rust compiler +cannot check if the declaration is correct, so specifying it correctly is part +of keeping the binding correct at runtime. The `extern` block can be extended to cover the entire snappy API: