Untangle pool abstract class from worker strategy selection (#234)

[poolifier.git] / README.md

diff --git a/README.md b/README.md
index ce026b148412eb6e445db1b6d6f53775af7bed2d..fe74335db7104991983bf100d06ff90001ae8d5f 100644 (file)
--- a/README.md
+++ b/README.md
@@ -203,7 +203,7 @@ We already have a bench folder where you can find some comparisons.
 Thread pools are built on top of Node.js [worker-threads](https://nodejs.org/api/worker_threads.html#worker_threads_worker_threads) module.
 
 **Cluster pools** (FixedClusterPool and DynamicClusterPool) are suggested to run I/O intensive tasks, again you can still run CPU intensive tasks into cluster pools, but performance enhancement is expected to be minimal.  
-Cluster pools are built on top of Node.js [cluster](https://nodejs.org/api/cluster.html) module.  
+Cluster pools are built on top of Node.js [cluster](https://nodejs.org/api/cluster.html) module.
 
 **Remember** that some Node.js tasks are execute by Node.js into the libuv worker pool at process level as explained [here](https://nodejs.org/en/docs/guides/dont-block-the-event-loop/#what-code-runs-on-the-worker-pool).