From 945cb331c4ed562de08402468ab266e4e246f9ce Mon Sep 17 00:00:00 2001
From: xiehan <52160700+Barenboim@users.noreply.github.com>
Date: Wed, 2 Jun 2021 00:39:12 +0800
Subject: [PATCH] Update FAQ.md

---
 docs/en/FAQ.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/FAQ.md b/docs/en/FAQ.md
index 338eff68..b72ecddc 100644
--- a/docs/en/FAQ.md
+++ b/docs/en/FAQ.md
@@ -93,7 +93,7 @@ int main(void)
 
 ### What is the life cycle of a task object?
 
-Each task in the framework (as well as **SeriesWork**) is given to you in the form of a bare pointer. The life cycle of each task object starts from the creation of the object and ends in the completion of the callback of that object. In other words, the task pointer is invalid after the callback, and all the data in that task are also destroyed. If you want to keep the data, you can use **std::move()** to move them. For example, the code below keeps **resp** in the HTTP task:
+Each task in the framework (as well as **SeriesWork**) is given to you in the form of a raw pointer. The life cycle of each task object starts from the creation of the object and ends in the completion of the callback of that object. In other words, the task pointer is invalid after the callback, and all the data in that task are also destroyed. If you want to keep the data, you can use **std::move()** to move them. For example, the code below keeps **resp** in the HTTP task:
 
 ~~~cpp
 void http_callback(WFHttpTask *task)