From 76fc01a698f10e0a9575a2ea25f687986d520ea3 Mon Sep 17 00:00:00 2001
From: Andy Maleh <23052+AndyObtiva@users.noreply.github.com>
Date: Thu, 22 Jun 2023 14:42:27 -0400
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9f5dafa93..473312df1 100644
--- a/README.md
+++ b/README.md
@@ -1360,7 +1360,7 @@ That is because Glimmer does everything that Shoes did, but with a lighter and b
 - Shoes does not allow code in Shoes blocks to use variables defined outside of Shoes blocks in a straightforward manner as it changes `self` inside Shoes blocks, breaking Ruby expectations and producing confusing behavior. On the other hand, Glimmer DSL blocks are 100% standard Ruby blocks that represent real closures, so they enable usage of variables defined outside the blocks in a 100% Ruby standard way.
 - Shoes lacks support for high-quality business widget controls (View components) like table and tree. Glimmer GUI DSLs that are feature complete like Glimmer DSL for SWT do support table and tree widgets. Some non-final Glimmer GUI DSLs like Glimmer DSL for LibUI support the table control too.
 - Shoes does not encourage proper separation of concerns with a correct MVC architecture (Model-View-Controller), resulting in a lot of non-presentation logic mixed with View code. Glimmer GUI DSLs do support proper separation of concerns 100% following the MVC or MVP (Model-View-Presenter) architecture by default.
-- Shoes does not provide a simple way for connecting View components to Model data. Glimmer provides full bidirectional/unidirectional data-binding support out of the box that provides the terest code syntax for connecting Views to Models and keeping them in sync.
+- Shoes does not provide a simple way for connecting View components to Model data. Glimmer GUI DSLs provide full bidirectional/unidirectional data-binding support out of the box that provides the terest code syntax for connecting Views to Models and keeping them in sync.
 - Shoes does not support a native mechanism for building custom View components. Glimmer does support the ability to build custom widgets (aka controls or View components), custom windows (aka shells), and custom shapes (canvas graphics). That results in much higher productivity by enabling the reuse of higher visual concepts as their own self-encapsulated components.
 - Shoes does not expose native features of its wrapped GUI toolkit. Glimmer GUI DSLs do expose all native features of their wrapped GUI toolkits, thus enabling developers to use a GUI toolkit like SWT directly when needed on top of using Glimmer DSL for SWT. That facilitates the 80/20 rule of having Glimmer GUI DSLs automate 80% of the work while still enabling software engineers to reach down to the low-level GUI toolkit API in 20% of the cases when needed (though in practice, it's probably more like 1% of the cases).