diff --git a/sections/errorhandling/usematurelogger.md b/sections/errorhandling/usematurelogger.md
index b46e424b..53b6ba6f 100644
--- a/sections/errorhandling/usematurelogger.md
+++ b/sections/errorhandling/usematurelogger.md
@@ -2,7 +2,7 @@
 
 ### One Paragraph Explainer
 
-We all loovve console.log but obviously a reputable and persisted Logger like [Winston][winston], [Bunyan][bunyan], [Pino][pino] or L4JS is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software
+We all loovve console.log but obviously a reputable and persisted Logger like [Winston][winston], [Bunyan][bunyan] (highly popular) or  [Pino][pino] (the new kid in town which is focused on performance) is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software
 (4) Expose and curate log statement for the operation team using operational intelligence tool like Splunk
 
 [winston]: https://www.npmjs.com/package/winston