From 696cba6e25fc7a8ee90e4db00f4df89dfe963d8e Mon Sep 17 00:00:00 2001
From: Ralf Jung <post@ralfj.de>
Date: Sat, 19 Oct 2019 10:14:10 +0200
Subject: [PATCH] the exampleis about drop, not (de)allocation

---
 src/liballoc/rc.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/liballoc/rc.rs b/src/liballoc/rc.rs
index 1cab8026514ea..205f0d7b40856 100644
--- a/src/liballoc/rc.rs
+++ b/src/liballoc/rc.rs
@@ -112,9 +112,9 @@
 //!
 //!     // Despite dropping `gadget_owner`, we're still able to print out the name
 //!     // of the `Owner` of the `Gadget`s. This is because we've only dropped a
-//!     // single `Rc<Owner>`, not the `Owner` allocation it points to. As long as there are
+//!     // single `Rc<Owner>`, not the `Owner` it points to. As long as there are
 //!     // other `Rc<Owner>` pointing at the same `Owner` allocation, it will remain
-//!     // allocated. The field projection `gadget1.owner.name` works because
+//!     // live. The field projection `gadget1.owner.name` works because
 //!     // `Rc<Owner>` automatically dereferences to `Owner`.
 //!     println!("Gadget {} owned by {}", gadget1.id, gadget1.owner.name);
 //!     println!("Gadget {} owned by {}", gadget2.id, gadget2.owner.name);