qualcomm-linux · sjakki88 · Feb 27, 2026 · Feb 27, 2026
diff --git a/media/k2c-qli-build-ga/ws_qsc_cli_2.png b/media/k2c-qli-build-ga/ws_qsc_cli_2.png
diff --git a/topic/k2c-qli-build-ga/acronyms_and_terms.rst b/topic/k2c-qli-build-ga/acronyms_and_terms.rst
@@ -52,5 +52,7 @@ Acronyms and terms
      - Software development kit
    * - UFS 
      - Universal flash storage
+   * - VM 
+     - Virtual machine
    * - WSL 
      - Windows Subsystem for Linux
diff --git a/topic/k2c-qli-build-ga/build_from_source_github.rst b/topic/k2c-qli-build-ga/build_from_source_github.rst
@@ -42,7 +42,7 @@ Install and configure the required software tools on the Ubuntu host computer.
 Sync
 -----
 
-QLI uses the kas tool to sync and build the Yocto meta layers. Kas lock files recording the meta layer repository information are stored in `meta-qcom-releases <https://github.com/qualcomm-linux/meta-qcom-releases>`__ for every critical release. 
+QLI uses the kas tool to sync and build the Yocto meta layers. For every critical release, Kas lock files record the meta-layer repository information in `meta-qcom-releases <https://github.com/qualcomm-linux/meta-qcom-releases>`__.
 
 You can checkout the lock files for each release using the `meta-qcom-release-tag`. The meta-qcom release tag follows the syntax ``qli-<version>``. For example, the meta-qcom release tag can be ``qli-2.0-rc1``, where ``2.0-rc1`` is the release version.
 

diff --git a/topic/k2c-qli-build-ga/build_own_config_cli.rst b/topic/k2c-qli-build-ga/build_own_config_cli.rst
@@ -27,8 +27,8 @@ When compiling a software image, ensure that you also compile the software produ
 
       This command opens the terminal.
 
-      .. note:: An environment is set up to run your own build commands for a specific software image. QSC won't track the status of input workspaces in the future releases and flash using ``qsc-cli`` won't be supported for these workspaces.
-
+      .. note:: An environment is set up to run your own build commands for a specific software image. QSC will not track the status of input workspaces in future releases, and you cannot flash these workspaces with ``qsc-cli``.
+         
    b. Update the highlighted command according to your own machine configuration and run it on the terminal:
 
       .. image:: ../../media/k2c-qli-build-ga/qsc-cli-open-build-terminal.png

diff --git a/topic/k2c-qli-build-ga/flash_images.rst b/topic/k2c-qli-build-ga/flash_images.rst
@@ -692,9 +692,7 @@ Flash software using PCAT
 
    The device reboots after the flashing procedure completes successfully. To verify the updated software version, see `Verify the Qualcomm Linux version <https://docs.qualcomm.com/bundle/publicresource/topics/80-80020-251/set_up_the_device.html#verify-the-qualcomm-linux-version>`__.
 
-.. note::
-   The correct camera driver and video driver may not be enabled by default for certain kits. To enable
-   them, see :doc:`this document <enable_dtb_overlay>`.
+.. note:: The correct camera driver and video driver may not be enabled by default for certain kits. To enable them, see :ref:`Enable camera overlays <enable_dtb_overlay>`.
 
 Related topics
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Original file line number
+Diff line change
@@ Expand Up @@
     Sync
     -----
-    QLI uses the kas tool to sync and build the Yocto meta layers. Kas lock files recording the meta layer repository information are stored in `meta-qcom-releases <https://github.com/qualcomm-linux/meta-qcom-releases>`__ for every critical release.
+    QLI uses the kas tool to sync and build the Yocto meta layers. For every critical release, Kas lock files record the meta-layer repository information in `meta-qcom-releases <https://github.com/qualcomm-linux/meta-qcom-releases>`__.
     You can checkout the lock files for each release using the `meta-qcom-release-tag`. The meta-qcom release tag follows the syntax ``qli-<version>``. For example, the meta-qcom release tag can be ``qli-2.0-rc1``, where ``2.0-rc1`` is the release version.
@@ Expand Down @@