From b41b2947d56ce8be0b927d59d766a23271b9dd37 Mon Sep 17 00:00:00 2001
From: Havvy <ryan.havvy@gmail.com>
Date: Mon, 22 May 2017 23:49:35 -0700
Subject: [PATCH] Suggested changes by birkenfeld

---
 src/libcore/ops.rs | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/src/libcore/ops.rs b/src/libcore/ops.rs
index dd1990784c4..4fb1f1757bb 100644
--- a/src/libcore/ops.rs
+++ b/src/libcore/ops.rs
@@ -157,9 +157,8 @@ use marker::Unsize;
 /// its `drop` method called. Then any fields the value contains will also
 /// be dropped recursively.
 ///
-/// Because of the recursive dropping, even for types that do not implement
-/// this trait, you do not need to implement this trait unless your type
-/// needs its own destructor logic.
+/// Because of the recursive dropping, you do not need to implement this trait
+/// unless your type needs its own destructor logic.
 ///
 /// # Examples
 ///
@@ -181,9 +180,8 @@ use marker::Unsize;
 /// ```
 ///
 /// Showing the recursive nature of `Drop`. When `outer` goes out of scope, the
-/// `drop` method will be called for `Outer` and then the `drop` method for
-/// `Inner` will be called. Therefore `main` prints `Dropping Outer!` and then
-/// `Dropping Inner!`.
+/// `drop` method will be called first for `Outer`, then for `Inner`. Therefore
+/// `main` prints `Dropping Outer!` and then `Dropping Inner!`.
 ///
 /// ```
 /// struct Inner;