Vaadin 8 terminology changes: Architecture Overview

Change-Id: I78a2a3a0a75527cf12c2c6d626272dc35bb18ba6

diff --git a/documentation/architecture/architecture-overview.asciidoc b/documentation/architecture/architecture-overview.asciidoc
index dee3a13fcf59d0b88a6c7bba6d97de2961451f58..3e4e7552b15423f8086777d6a45d5abd06b56cd1 100644 (file)
--- a/documentation/architecture/architecture-overview.asciidoc
+++ b/documentation/architecture/architecture-overview.asciidoc
@@ -127,15 +127,12 @@ Data Binding:: ((("Data
 Model")))
 ((("Data
 Binding")))
-In addition to the user interface model, Vaadin provides a __data model__ for
-binding data presented in field components, such as text fields, check boxes and
-selection components, to a data source. Using the data model, the user interface
+In addition to the user interface model, Vaadin provides a __data binding__ API for
+associating data presented in field components, such as text fields, check boxes and
+selection components, with a data source. Using data binding, the user interface
 components can update the application data directly, often without the need for
-any control code. All the field components in Vaadin use this data model
-internally, but any of them can be bound to a separate data source as well.
-((("SQL")))
-For example, you can bind a table component to an SQL query response. For a
-complete overview of the Vaadin Data Model, please refer to
+any control code. For example, you can bind a data grid component to a backend query
+response. For a complete overview of the data binding model, please refer to
 <<dummy/../../../framework/datamodel/datamodel-overview.asciidoc#datamodel.overview,"Binding
 Components to Data">>.