From 7ded7f764c2d590d0c3ad71b9ffbbcfaec2174fb Mon Sep 17 00:00:00 2001 From: Christian Poveda Date: Sat, 24 Feb 2018 18:06:01 -0500 Subject: [PATCH] corrected grammar errors --- src/libcore/cell.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/libcore/cell.rs b/src/libcore/cell.rs index 91074c18d771..858bdcbb7211 100644 --- a/src/libcore/cell.rs +++ b/src/libcore/cell.rs @@ -10,17 +10,17 @@ //! Shareable mutable containers. //! -//! Rust memory safety is based on this rule: Given an object `T`, is only possible to +//! Rust memory safety is based on this rule: Given an object `T`, it is only possible to //! have one of the following: //! -//! - Having several inmutable references (`&T`) to the object (also know as Aliasing). +//! - Having several immutable references (`&T`) to the object (also know as Aliasing). //! - Having one mutable reference (`&mut T`) to the object (also know as Mutability). //! //! This is enforced by the Rust compiler. However, there are situations where this rule is not -//! flexible enough. Sometimes is required to have multiple references to an object and yet +//! flexible enough. Sometimes it is required to have multiple references to an object and yet //! mutate it. //! -//! Shareable mutable containers exist to permit mutability in presence of aliasing in a +//! Shareable mutable containers exist to permit mutability in the presence of aliasing in a //! controlled manner. Both `Cell` and `RefCell` allows to do this in a single threaded //! way. However, neither `Cell` nor `RefCell` are thread safe (they do not implement //! `Sync`), if you need to do Aliasing and Mutation between multiple threads is possible to use