Small documentation correction (from github).

Original pull request is https://github.com/vaadin/vaadin/pull/68.

Change-Id: If6dd0490a52cab3fc0bf59224546e0d295fe666c

diff --git a/documentation/application/application-architecture.asciidoc b/documentation/application/application-architecture.asciidoc
index 5b945e9abcad749b6591142d35b4fa53be16a012..15f0dcbafbf8635c555b53cf93fd114f9e92b0e1 100644 (file)
--- a/documentation/application/application-architecture.asciidoc
+++ b/documentation/application/application-architecture.asciidoc
@@ -178,8 +178,8 @@ with CustomComponent">>.
 [[application.architecture.navigation]]
 == View Navigation
 
-While the most simple applications have just a single __view__ (or __screen__),
-perhaps most have many. Even in a single view, you often want to have sub-views,
+While the simplest applications have just one __view__ (or __screen__), most of them often require several.
+Even in a single view, you often want to have sub-views,
 for example to display different content.
 <<figure.application.architecture.navigation>> illustrates a typical navigation
 between different top-level views of an application, and a main view with