about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMaxim Nazarenko <nz.phone@mail.ru>2018-02-27 16:41:28 +0200
committerMaxim Nazarenko <nz.phone@mail.ru>2018-02-27 16:41:28 +0200
commit273166e7655dc736f444de43505c3ddda5c742f7 (patch)
treeaf1c83c530eec573c77c364ce42662f8639f16f2
parentb9b82490206fc41eb10662d6847a1ad28618ee59 (diff)
downloadrust-273166e7655dc736f444de43505c3ddda5c742f7.tar.gz
rust-273166e7655dc736f444de43505c3ddda5c742f7.zip
remove italic
remove italic as per @GuillaumeGomez suggestion
-rw-r--r--src/libcore/cell.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libcore/cell.rs b/src/libcore/cell.rs
index 6f91e743999..4a1d68efc99 100644
--- a/src/libcore/cell.rs
+++ b/src/libcore/cell.rs
@@ -1164,8 +1164,8 @@ impl<'a, T: ?Sized + fmt::Display> fmt::Display for RefMut<'a, T> {
 /// The compiler makes optimizations based on the knowledge that `&T` is not mutably aliased or
 /// mutated, and that `&mut T` is unique. When building abstractions like `Cell`, `RefCell`,
 /// `Mutex`, etc, you need to turn these optimizations off. `UnsafeCell` is the only legal way
-/// to do this. When `UnsafeCell<T>` _itself_ is immutably aliased, it is still safe to obtain
-/// a mutable reference to its _interior_ and/or to mutate the interior. However, it is up to
+/// to do this. When `UnsafeCell<T>` itself is immutably aliased, it is still safe to obtain
+/// a mutable reference to its interior and/or to mutate the interior. However, it is up to
 /// the abstraction designer to ensure that no two mutable references obtained this way are active
 /// at the same time, there are no active immutable reference when a mutable reference is obtained
 /// from the cell, and that there are no active mutable references or mutations when an immutable