femperor
diff --git a/‎README.md‎
Lines changed: 4 additions & 4 deletions b/‎README.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎doc/faq.md‎
Lines changed: 8 additions & 4 deletions b/‎doc/faq.md‎
Lines changed: 8 additions & 4 deletions
diff --git a/‎example/simple.cpp‎
Lines changed: 1 addition & 1 deletion b/‎example/simple.cpp‎
Lines changed: 1 addition & 1 deletion
@@ -32,7 +32,7 @@ and is by far faster, more expressive, and easier for drop-in integration than e
 The following example [simple.cpp](./example/simple.cpp) shows the basic API you need to use Cpp-Taskflow.
 
 ```cpp
-#include "taskflow.hpp"  // the only include you need
+#include <taskflow.hpp>  // the only include you need
 
 int main(){
 
@@ -195,7 +195,7 @@ auto B = tf.silent_emplace([] (auto& subflow) {
   auto B3 = subflow.silent_emplace([](){}).name("B3");
   B1.precede(B3);
   B2.precede(B3);
-}).name("TaskB");
+}).name("B");
 
 A.precede(B);  // B runs after A 
 A.precede(C);  // C runs after A 
@@ -208,7 +208,7 @@ std::cout << tf.dump_topologies();
 ```
 
 By default, a subflow graph joins to its parent node. 
-This guarantees a subflow graph to finish before executing the successors of 
+This guarantees a subflow graph to finish before the successors of 
 its parent node.
 You can disable this feature by calling `subflow.detach()`.
 Detaching the above subflow will result in the following execution flow.
@@ -231,7 +231,7 @@ Detaching the above subflow will result in the following execution flow.
 
 Cpp-Taskflow has an unified interface for static and dynamic tasking.
 To create a subflow for dynamic tasking, 
-emplace a task callable with one argument of type `tf::SubflowBuilder`.
+emplace a callable on one argument of type `tf::SubflowBuilder`.
 
 ```cpp
 auto A = tf.silent_emplace([] (tf::SubflowBuilder& subflow) {});
 
@@ -11,6 +11,14 @@ If you cannot find a solution here, please post an issue [here][Github issues].
 It has been applied in many academic and industry projects to scale up their existing workload.
 A research project [OpenTimer][OpenTimer] has used Cpp-Taskflow to deal with hundreds of millions of tasks.
 
+### Q: What are the differences between Cpp-Taskflow and other tasking libraries?
+
+**A:** From our humble opinion, Cpp-Taskflow is superior in its tasking API, interface, and performance.
+In most cases, users can quickly master Cpp-Taskflow to create large and complex dependency graphs
+in just a few minutes.
+The performance scales very well and is comparable to hard-coded multi-threading.
+Of course, the judge is always left for users -:)
+
 ## Compile Issues
 
 ### Q: I can't get Cpp-Taskflow compiled in my project!
@@ -59,10 +67,6 @@ Try the `dump` method to debug the graph before dispatching your taskflow graph.
 If there is no cycle, make sure you are using `future.get()` in the right way, 
 i.e., not blocking your control flow.
 
-
-
-
-
 * * *
 [Github issues]:         https://github.com/cpp-taskflow/cpp-taskflow/issues
 [OpenTimer]:             https://github.com/OpenTimer/OpenTimer
 
@@ -3,7 +3,7 @@
 // TaskA---->TaskB---->TaskD
 // TaskA---->TaskC---->TaskD
 
-#include "taskflow.hpp"  // the only include you need
+#include <taskflow.hpp>  // the only include you need
 
 int main(){