Update documentation, BoV chapters 1 - 5.3 (#8085)

* Update documentation chapters 1 - 5.3

Images and diagrams have not been updated,
but unnecessary images have been removed.

* Sync application declarative and architecture sections source code.

Screenshot image is updated to match the source code.

* Old datamodel image is removed.

* Ivy install image is removed.

* Remove unnecessary linking / reference

3 files changed, 6 insertions, 29 deletions

diff --git a/documentation/introduction/intro-background.asciidoc b/documentation/introduction/intro-background.asciidoc
index ef0138494f..5a359b05b7 100644
--- a/documentation/introduction/intro-background.asciidoc
+++ b/documentation/introduction/intro-background.asciidoc
@@ -90,12 +90,12 @@ steering committee. As a member of the committee, Vaadin can work towards the
 success of GWT as a foundation of the Java web development community.
 
 [[intro.background.vaadin8]]
-== Vaadin 8 Introduces New Data Binding API
+== Vaadin Framework 8 with New Data Binding API
 
-The biggest change in Vaadin 8 is the complete modernization of the data binding API.
-Binding components to data sources is one of the core features of the Vaadin Framework, as it eliminates the need to explicitly shuffle data between Vaadin components and data objects, typically beans.
+The biggest change in Vaadin Framework 8 is the complete modernization of the data binding API.
+Binding components to data sources is one of the core features of the Vaadin Framework, as it eliminates the need to explicitly shuffle data between components and data objects, typically beans.
 The old data model was designed in time before Java features such as generics.
 While the data model was improved over the years, it was fundamentally outdated and complex to use.
-The new data binding API works much more fluently in Java 8, especially with Java 8 features such as lambda expressions.
+The new data binding API works much more fluently in Java 8, especially with Java 8 features such as lambda expressions and streams.
 Consequently, to be able to fully use the new features of Java 8, we have raised the requirements from Java 6 to 8.
-The change should make Vaadin up to date with the most current Java technologies used by developers.
+The change should make Vaadin Framework up to date with the most current Java technologies used by developers.
diff --git a/documentation/introduction/intro-goals.asciidoc b/documentation/introduction/intro-goals.asciidoc
index e2173b0875..e023525eda 100644
--- a/documentation/introduction/intro-goals.asciidoc
+++ b/documentation/introduction/intro-goals.asciidoc
@@ -19,7 +19,7 @@ following rules.
 
 Because our goals are high, the focus must be clear. Vaadin is designed for
 creating web applications. It is not designed for creating websites or
-advertisement demos. You may find, for example, JSP/JSF or Flash more suitable
+advertisement demos. You may find, for example, JSP/JSF more suitable
 for such purposes.
 
 
diff --git a/documentation/introduction/intro-walkthrough.asciidoc b/documentation/introduction/intro-walkthrough.asciidoc
index ad3519ccd7..185498f627 100644
--- a/documentation/introduction/intro-walkthrough.asciidoc
+++ b/documentation/introduction/intro-walkthrough.asciidoc
@@ -18,7 +18,6 @@ import com.vaadin.ui.Label;
 import com.vaadin.ui.UI;
 
 @Title("My UI")
-@Theme("valo")
 public class HelloWorld extends UI {
     @Override
     protected void init(VaadinRequest request) {
@@ -69,25 +68,3 @@ deploy it to a server, as explained in
 <<dummy/../../../framework/application/application-environment#application.environment,"Deploying
 an Application">>. During development, you typically deploy to an application
 server integrated with the IDE.
-
-Developing a pure client-side application, you could write a Hello World just as
-easily, and also in Java:
-
-
-[source, java]
-----
-public class HelloWorld implements EntryPoint {
-    @Override
-    public void onModuleLoad() {
-        RootPanel.get().add(new Label("Hello, world!"));
-    }
-}
-----
-
-We do not set the title here, because it is usually defined in the HTML page in
-which the code is executed. The application would be compiled into JavaScript
-with the Vaadin Client Compiler (or GWT Compiler). It is more typical, however,
-to write client-side widgets, which you can then use from a server-side Vaadin
-application. For more information regarding client-side development, see
-<<dummy/../../../framework/clientside/clientside-overview.asciidoc#clientside.overview,"Client-Side
-Vaadin Development">>.