From f694b7f8472ea9ecbfcd4f9753fb0b046e05f408 Mon Sep 17 00:00:00 2001
From: Hsu Still <341464@gmail.com>
Date: Sun, 8 Apr 2018 01:29:50 +0800
Subject: [PATCH] Simplify RuntimeResult section

---
 docs/guides/commands/post-execution.md | 22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)

diff --git a/docs/guides/commands/post-execution.md b/docs/guides/commands/post-execution.md
index e1bd62c11..5f19147cb 100644
--- a/docs/guides/commands/post-execution.md
+++ b/docs/guides/commands/post-execution.md
@@ -52,19 +52,15 @@ next? We can take this further by using [RuntimeResult].
 
 ### RuntimeResult
 
-This class was introduced in 1.0, but it wasn't widely adopted due to
-the aforementioned [ExecuteAsync] drawback. Since we now have
-access to a proper result-handler via the [CommandExecuted] event,
-we can start making use of this class.
-
-#### What is it?
-
-`RuntimeResult` was introduced to allow developers to centralize
-their command result logic. In other words, it is a result type
-that is designed to be returned when the command has finished its
-execution.
-
-#### How to make use of it?
+`RuntimeResult` was originally introduced in 1.0 to allow
+developers to centralize their command result logic.
+In other words, it is a result type that is designed to be
+returned when the command has finished its execution.
+
+However, it wasn't widely adopted due to the aforementioned
+[ExecuteAsync] drawback. Since we now have access to a proper
+result-handler via the [CommandExecuted] event, we can start
+making use of this class.
 
 The best way to make use of it is to create your own version of
 `RuntimeResult`. You can achieve this by inheriting the `RuntimeResult`