From 0da819c106515708ae695752b6f2bf9fb5d9e98c Mon Sep 17 00:00:00 2001
From: Shimmy <2716316+weitzhandler@users.noreply.github.com>
Date: Mon, 5 Jun 2023 03:38:33 +0100
Subject: [PATCH] docs(mvux): Minor edits

---
 doc/Overview/Mvux/Overview.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/Overview/Mvux/Overview.md b/doc/Overview/Mvux/Overview.md
index 1b970f0990..b19f90468d 100644
--- a/doc/Overview/Mvux/Overview.md
+++ b/doc/Overview/Mvux/Overview.md
@@ -54,7 +54,7 @@ In the standard MVU pattern, an update will cause a new View to be created upon
 
 ### eXtended
 
-The **eXtended** part of the pattern includes the toolset to adapt between the data-binding engine and the Model which includes code generation and UI controls.
+The **eXtended** part of the pattern includes the toolset to adapt between the data-binding engine and the Model, which consists of generated code and and UI controls.
 
 ## Using MVUX to create an app
 
@@ -131,7 +131,6 @@ Update is also when states are updated with new values this is not used in this
 The question is if we want to expose the use of IState in this introduction
 -->
 
-
 ### Result
 
 When the app is lanuched, a waiting progress ring appears while the service loads the current temperature: