From 8db46ff762e21d14f6b961bd2c6b071f230ff9fd Mon Sep 17 00:00:00 2001
From: erelling <54530323+erelling@users.noreply.github.com>
Date: Fri, 8 Nov 2019 01:57:18 +0100
Subject: [PATCH] Update n00b-overview.md

---
 docs/n00b-overview.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/n00b-overview.md b/docs/n00b-overview.md
index 24351b97d..a9c5024f7 100644
--- a/docs/n00b-overview.md
+++ b/docs/n00b-overview.md
@@ -17,11 +17,11 @@ And end up with this in the documentation:
 
 Most of the stuff I need to visualize can be scripted in a similar way, with a varitety of different symbols and chart types available. Since the diagram source is text based, it can be part of production scripts (and other pieces of code). So less time needs be spent on documenting as a separate task.
 
-Comparing with Visio and similar applications, mermaid is a really fast and simple way to create good visualizations. This is especially apparent when a complex visualisation needs to be edited, which could take me hours in a desktop application.
+Comparing with Visio and similar applications, mermaid is a really fast way to create good visualizations. This is especially apparent when a complex visualisation needs to be edited, which could take me hours in a desktop application.
 
-With mermaid I can spend a fraction of that time automating the diagram generation and end up saving even more time. I love it!
+With mermaid I can spend a fraction of that time instead automating the diagram generation and end up saving even more time. I love it!
 
 
 However, a lot of the mermaid documentation is geared to professional frontend developers, presuming a skill set which I simply do not have.
 
-I needed a really basic instruction, and here it is.
+I needed a really basic instruction. And here it is.