review

website/documentation/content/overview.py

@@ -37,19 +37,19 @@
     Your app assembles these components into _pages_.
     When the user interacts with an item on a page, NiceGUI triggers an _event_ (or _action_).
     You define code to _handle_ each event, such as what to do when a user clicks a button, modifies a value or operates a slider.
-    Elements can also be bound to a _model_ (data object), which automatically updates the user interface when the value changes.
+    Elements can also be bound to a _model_ (data object), which automatically updates the user interface when the model value changes.
 
     Elements are arranged on a page using a "declarative UI" or "code-based UI".
     That means that you also write structures like grids, cards, tabs, carousels, expansions, menus, and other layout elements directly in code.
     This concept has been made popular with Flutter and SwiftUI.
-    For readability, NiceGUI utilizes Pythons `with ...` statement.
-    This context mangers provides a nice way to indent the code to resemble the layout of the UI.
+    For readability, NiceGUI utilizes Python's `with ...` statement.
+    This context manager provides a nice way to indent the code to resemble the layout of the UI.
 
     Styling and appearance can be controlled in several ways.
-    Most elements accepts optional arguments for common styling and behavior changes, such as icons on buttons or color of a text.
+    Most elements accept optional arguments for common styling and behavior changes, such as button icons or text color.
     Because NiceGUI is a web framework, you can change almost any appearance of an element with CSS.
     But elements also provide `.classes` and `.props` methods to apply Tailwind CSS and Quasar properties
-    which are more high level and simpler to use day-to-day after you get the hang of it.
+    which are more high-level and simpler to use day-to-day after you get the hang of it.
 ''')
 
 doc.text('Actions, Events and Tasks', '''