From 7084ff8775756a7163bf90808a412c5896c32fa3 Mon Sep 17 00:00:00 2001
From: Adnan ELARAJI <7360655+aelaraji@users.noreply.github.com>
Date: Thu, 9 May 2024 19:55:00 +0100
Subject: [PATCH] Fix typo in README.md file

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 9ca9877..95d5f4b 100644
--- a/README.md
+++ b/README.md
@@ -51,7 +51,7 @@ EOF
 zs serve
 ```
 
-For a starter template see the [zs-starter-template](https://git.mills.io/prologic/zs-stater-template) which can also be found running live at [zs.mills.io](https://zs.mills.io).
+For a starter template see the [zs-starter-template](https://git.mills.io/prologic/zs-starter-template) which can also be found running live at [zs.mills.io](https://zs.mills.io).
 
 ## Features
 
@@ -99,7 +99,7 @@ Markdown text goes after a header *separator*
 ```
 
 Use placeholders for variables and plugins in your markdown or html
-files, e.g. `{{ title }}` or `{{ command arg1 arg2 }}.
+files, e.g. `{{ title }}` or `{{ command arg1 arg2 }}`.
 
 Write extensions in any language you like and put them into the `.zs`
 sub-directory.
@@ -159,7 +159,7 @@ For a full-list of default extensions enabled, see `zs --help` and the `-e/--ext
 Plugins are just executables in any language that output content. They can be system executables like `data` or custom scripts or programs that you place in `.zs/`. To use a plugins simply reference it in your content like so:
 
 ```markdown
-Site last updated at {{{ date }}
+Site last updated at {{ date }}
 ```
 
 or: