diff options
| author | Tshepang Lekhonkhobe <tshepang@gmail.com> | 2014-08-24 04:24:25 +0200 |
|---|---|---|
| committer | Tshepang Lekhonkhobe <tshepang@gmail.com> | 2014-08-24 04:24:25 +0200 |
| commit | 3e94401a6411001c7495a13dcbb289cb3935994f (patch) | |
| tree | 2e29e915ac3193f2229ccc883952f2d79bdef7e6 | |
| parent | 36131f5be403e3f89c45627498bea535d94cb619 (diff) | |
doc: move misplaced comma
Also: * Remove unseeming repetition. * By now, the reader has already heard that Rust is safe by default, so reduce the overlong sentence, making it easier to read.
| -rw-r--r-- | src/doc/guide.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/guide.md b/src/doc/guide.md index f1211c0788e..fad1dd31e68 100644 --- a/src/doc/guide.md +++ b/src/doc/guide.md @@ -5531,9 +5531,9 @@ There are two circumstances where Rust's safety provisions don't work well. The first is when interfacing with C code, and the second is when building certain kinds of abstractions. -Rust has support for FFI, (which you can read about in the [FFI -Guide](guide-ffi.html)) but Rust can't guarantee that the C code will be safe, -like Rust's will. Therefore, Rust marks such functions with the `unsafe` +Rust has support for FFI (which you can read about in the [FFI +Guide](guide-ffi.html)), but can't guarantee that the C code will be safe. +Therefore, Rust marks such functions with the `unsafe` keyword, which indicates that the function may not behave properly. Second, if you'd like to create some sort of shared-memory data structure, Rust |