From d0c9b5e98f53216e11ec86090371bb995fd3eea8 Mon Sep 17 00:00:00 2001
From: Erik Ellingsen <erike@Eriks-iMac.local>
Date: Fri, 8 Nov 2019 10:35:38 +0100
Subject: [PATCH] grammar

---
 docs/n00b-gettingStarted.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/n00b-gettingStarted.md b/docs/n00b-gettingStarted.md
index 8fc531eca..e3ec5d561 100644
--- a/docs/n00b-gettingStarted.md
+++ b/docs/n00b-gettingStarted.md
@@ -160,7 +160,7 @@ mermaid content...
 ---
 
 **Three additional comments from Knut Sveidqvist, creator of mermaid:**
-- In early versions of mermaid, the `<script src>` tag was invoked in the `<head>` part of the web page. Nowdays we can place it directly in `<body>` as seen above. However, older parts of the documentation frequently reflects the old way which still works.
+- In early versions of mermaid, the `<script src>` tag was invoked in the `<head>` part of the web page. Nowdays we can place it directly in `<body>` as seen above. However, older parts of the documentation frequently reflects the previous way which still works.
   
 - We initialize the mermaid rendering with `mermaid.initialize()` directly in the html code. In principle this could be done through placing `mermaid.initialize()` inside of `mermaid.min.js`. We would then eliminate the need for this explicit line in the html. However, there are use cases where we do want to separate the two steps. Sometimes we want full control over when we start looking for `<div>`tags inside the web page with `mermaid.initialize()`, for example when we think that all `<div>` tags may not have loaded when `mermaid.min.js` runs.
 
