From f2e083156ecb77f6d933409fbe685403950a3685 Mon Sep 17 00:00:00 2001 From: Juha Vuolle Date: Thu, 22 Aug 2024 10:42:46 +0300 Subject: [PATCH] Fix minor Android manifest documentation issues Change-Id: I0b7a8a88acd7c6fd30ce67cc140a819c9e72862f Reviewed-by: Assam Boudjelthia (cherry picked from commit 1b963f02c102750af807ec08b04ab54986a35e8d) Reviewed-by: Qt Cherry-pick Bot --- .../doc/src/android-manifest-file-configuration.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/android/templates/doc/src/android-manifest-file-configuration.qdoc b/src/android/templates/doc/src/android-manifest-file-configuration.qdoc index d32d16aa470..407a10c8920 100644 --- a/src/android/templates/doc/src/android-manifest-file-configuration.qdoc +++ b/src/android/templates/doc/src/android-manifest-file-configuration.qdoc @@ -10,7 +10,7 @@ \nextpage android-services.html The Android Manifest is an XML file necessary for any Android app. It contains -app configuration for different settings and features that the app use, as well +app configuration for different settings and features that the app uses, as well as details on the app itself, such as, package name, app name, version, etc. Permissions and hardware features can also be set from the manifest. @@ -229,7 +229,7 @@ The main ones are: Different Qt modules might require some Android permissions or features to function properly, for example, Camera permission in \l {QtMultimedia}. -l{The androiddeployqt Tool} takes care of including such requirements into the +\l{The androiddeployqt Tool} takes care of including such requirements into the Android manifest during the build. Qt defines the following lines into the manifest, which they get replaced by the actual values: