From 254ee79c1d7304a5e2264d45ec094ce42b64ccf3 Mon Sep 17 00:00:00 2001
From: Henri Sara <henri.sara@gmail.com>
Date: Thu, 27 Apr 2017 13:29:46 +0300
Subject: Add documentation for Composite

---
 documentation/application/application-architecture.asciidoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'documentation/application/application-architecture.asciidoc')

diff --git a/documentation/application/application-architecture.asciidoc b/documentation/application/application-architecture.asciidoc
index c2dec0443e..5e87ea8531 100644
--- a/documentation/application/application-architecture.asciidoc
+++ b/documentation/application/application-architecture.asciidoc
@@ -117,8 +117,8 @@ While extending layouts is an easy way to make component composition, it is a
 good practice to encapsulate implementation details, such as the exact layout
 component used. Otherwise, the users of such a composite could begin to rely on
 such implementation details, which would make changes harder. For this purpose,
-Vaadin has a special [classname]#CustomComponent# wrapper, which hides the
-content representation.
+Vaadin has the special wrappers [classname]#Composite# and
+[classname]#CustomComponent#, which hide the content representation.
 
 
 [source, java]
@@ -144,9 +144,9 @@ class MyView extends CustomComponent {
 MyView myview = new MyView();
 ----
 
-For a more detailed description of the [classname]#CustomComponent#, see
+For a more detailed description of [classname]#Composite# and [classname]#CustomComponent#, see
 <<dummy/../../../framework/components/components-customcomponent#components.customcomponent,"Composition
-with CustomComponent">>.
+with Composite and CustomComponent">>.
 
 
 [[application.architecture.navigation]]
-- 
cgit v1.2.3

