Merge remote-tracking branch 'origin/1.2' into dev5.51.3

Change-Id: I719253298a760e88a6ebab0cbf27e35cecc418a9

1 files changed, 5 insertions, 5 deletions

diff --git a/examples/enginio/quick/image-gallery/doc/src/image-gallery.qdoc b/examples/enginio/quick/image-gallery/doc/src/image-gallery.qdoc
index 51e7f1a..8d37fad 100644
--- a/examples/enginio/quick/image-gallery/doc/src/image-gallery.qdoc
+++ b/examples/enginio/quick/image-gallery/doc/src/image-gallery.qdoc
@@ -35,7 +35,7 @@
     and a button to upload more images.
     \image image-gallery.png
 
-    \section1 Backend configuration
+    \section1 Backend Configuration
     The Enginio backend needs to be set up to get this example working.
 
     Go to the Enginio Dashboard and create a new backend with the \c{Image Gallery} template.
@@ -62,19 +62,19 @@
     Copy the \e {backend id} from the Enginio dashboard.
     They need to be entered into the example when it is executed for the first time.
 
-    \section1 The example code
+    \section1 The Example Code
 
-    The first step is to set up the \l Enginio::EnginioClient client.
+    The first step is to set up the \l {EnginioClient} {Enginio client}.
     \snippet image-gallery/image-gallery.qml client
 
-    The model gets initialized with the client declared above.
+    Then the model is initialized with that client.
     \snippet image-gallery/image-gallery.qml model
 
     A delegate is needed to present the images nicely.
     The model is used to get the list of image objects, but the images
     are only attached to the objects as file references.
     Thus the image's thumbnail is fetched by each delegate.
-    \note in a real application it might be necessary to cache the images.
+    \note In a real application it might be necessary to cache the images.
 
     The \c Component.onCompleted function is used to fetch the image.
     When the delegate is created, it has the JSON image object data.