From bfce837c3d9a6e3ad850436b954f9a447e80d4d6 Mon Sep 17 00:00:00 2001 From: Topi Reinio Date: Mon, 11 Aug 2014 15:34:21 +0200 Subject: Doc: Remove duplicated words Removes duplicated (repeated) words and fixes other minor documentation issues. Change-Id: I891f2b3e60194b207737425c1dcc1d35a5bd921a Reviewed-by: Leena Miettinen --- src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc | 6 +++--- src/quick/doc/src/concepts/positioning/righttoleft.qdoc | 2 +- src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) (limited to 'src/quick/doc') diff --git a/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc b/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc index 1a539f56ed..85d34e5376 100644 --- a/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc +++ b/src/quick/doc/src/concepts/modelviewsdata/modelview.qdoc @@ -117,9 +117,9 @@ To visualize data, bind the view's \c model property to a model and the The ListView type has the \c section \l{qtqml-syntax-objectattributes.html#Attached-properties-and-attached-signal-handlers} {attached property} that can combine adjacent and related types into a - section. The section's \c property property is for selecting which list - type property to use as sections. The \c criteria can dictate how the - section names are displayed and the \c delegate is similar to the views' + section. The \c section.property determines which list + type property to use as sections. The \c section.criteria can dictate how the + section names are displayed and the \c section.delegate is similar to the views' \l {qml-view-delegate}{delegate} property. \snippet qml/listview-sections.qml section \image listview-section.png diff --git a/src/quick/doc/src/concepts/positioning/righttoleft.qdoc b/src/quick/doc/src/concepts/positioning/righttoleft.qdoc index c90aa3af22..8f55cc8dd7 100644 --- a/src/quick/doc/src/concepts/positioning/righttoleft.qdoc +++ b/src/quick/doc/src/concepts/positioning/righttoleft.qdoc @@ -42,7 +42,7 @@ from the right to left. The general rule of thumb is that content (like photos, mirrored, but positioning of the content (like application layouts and the flow of visual elements) is mirrored. For example, photos shown in chronological order should flow from right to left, the low end range of the horizontal sliders should be located at the right side of the slider, and -text lines should should be aligned to the right side of the available text area. The location of visual +text lines should be aligned to the right side of the available text area. The location of visual elements should not be mirrored when the position is related to a content; for example, when a position marker is shown to indicate a location on a map. Also, there are some special cases you may need to take into account where right-to-left language speakers are used to left-to-right diff --git a/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc b/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc index f07d981e5f..046c23f8f0 100644 --- a/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc +++ b/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc @@ -294,7 +294,7 @@ when to call the signals and this is the only time the OpenGL application is allowed to draw. The \l {Scene Graph - OpenGL Under QML} example gives an example on -how to use use these signals. +how to use these signals. The other alternative is to create a QQuickFramebufferObject, render into it, and let it be displayed in the scene graph as a texture. -- cgit v1.2.3