From 71c6759a36a015d65d078c0aedb09c8dadc2d3aa Mon Sep 17 00:00:00 2001
From: imadhui <111036389+imadhui@users.noreply.github.com>
Date: Wed, 31 Aug 2022 23:01:33 +0530
Subject: [PATCH] just a couple of typos

---
 CONCEPT.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CONCEPT.md b/CONCEPT.md
index 90f3ebe..f24bb02 100644
--- a/CONCEPT.md
+++ b/CONCEPT.md
@@ -32,7 +32,7 @@ There are three ways to establish the initial state of a user interface.
 1. Using an initial boot file served via http to establish the intial
 UI. This is near identical to traditional webservers/website solutions
 and every familiar technology offered for website development may be
-included in the booy file. Any html file with the boot.js script
+included in the boot file. Any html file with the boot.js script
 included or embedded may serve as a boot file to allow server side
 control with in the CLOG framework. The CLOG server and the server
 webpages must exist on the same domain do to security restrictions in
@@ -54,7 +54,7 @@ advantages for a completely non-html non-js code based.
 
 CLOG offers an event based framework. As of CLOG 1.2, an additional
 "presentations" like system is included for bidirectionally binding
-Lisp Objects and CLOG Objects and contiued development in CLOG is to
+Lisp Objects and CLOG Objects and continued development in CLOG is to
 pursue natural use with no or minimal use of CLOG Apis for data models
 and business logic.