From 4a390a1983cce591fb0f6e7b8b4ebc75813d5958 Mon Sep 17 00:00:00 2001
From: Trustin Lee <trustin@gmail.com>
Date: Thu, 3 Jun 2010 09:01:46 +0000
Subject: [PATCH] More Javadoc

---
 .../jboss/netty/handler/execution/ExecutionHandler.java   | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/main/java/org/jboss/netty/handler/execution/ExecutionHandler.java b/src/main/java/org/jboss/netty/handler/execution/ExecutionHandler.java
index 0b449234a6..831a828bce 100644
--- a/src/main/java/org/jboss/netty/handler/execution/ExecutionHandler.java
+++ b/src/main/java/org/jboss/netty/handler/execution/ExecutionHandler.java
@@ -38,10 +38,10 @@ import org.jboss.netty.util.internal.ExecutorUtil;
  * <p>
  * {@link ExecutionHandler} is often used when your {@link ChannelHandler}
  * performs a blocking operation that takes long time or accesses a resource
- * which is not CPU-bound.  Running such operations in a pipeline without an
- * {@link ExecutionHandler} will result in unwanted hiccup during I/O because
- * an I/O thread cannot perform I/O until your handler returns the control to
- * the I/O thread.
+ * which is not CPU-bound business logic such as DB access.  Running such
+ * operations in a pipeline without an {@link ExecutionHandler} will result in
+ * unwanted hiccup during I/O because an I/O thread cannot perform I/O until
+ * your handler returns the control to the I/O thread.
  * <p>
  * In most cases, an {@link ExecutionHandler} is coupled with an
  * {@link OrderedMemoryAwareThreadPoolExecutor} because it guarantees the