summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDenis Anisimov <denis@vaadin.com>2016-11-07 12:39:29 +0200
committerVaadin Code Review <review@vaadin.com>2016-11-11 19:49:01 +0000
commitd803404e97ce90c70ece758c6ea5f0375a860296 (patch)
tree31fe9b02f39320ee6710018a85a8dd9d81288fc0
parent55ac10703f033dcd444d20f9be419be3e91aa73f (diff)
downloadvaadin-framework-d803404e97ce90c70ece758c6ea5f0375a860296.tar.gz
vaadin-framework-d803404e97ce90c70ece758c6ea5f0375a860296.zip
Small documentation correction (from github).
Original pull request is https://github.com/vaadin/vaadin/pull/68. Change-Id: If6dd0490a52cab3fc0bf59224546e0d295fe666c
-rw-r--r--documentation/application/application-architecture.asciidoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/application/application-architecture.asciidoc b/documentation/application/application-architecture.asciidoc
index 5b945e9abc..15f0dcbafb 100644
--- 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