Removed typos

Removed passive voice in statements

Signed-off-by: Vinay Jaassiel Kankipati <vinayjk@qti.qualcomm.com>

Author: vinaykankipati

topic/k2c-qli-build-ga/addn_host_setup_build_firmware.rst

@@ -16,7 +16,7 @@ Install and configure the software tools on the Ubuntu host computer.
          pipx ensurepath
          pipx install kas
 
-#. Optionally download the kas-container script. kas is the tool used by Qualcomm Linux to sync and build the Yocto meta layers. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated evironment, consider using kas-container instead.
+#. Optionally download the kas-container script. kas is the tool used by Qualcomm Linux to sync and build the Yocto meta layers. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated environment, consider using kas-container instead.
 
    .. container:: nohighlight
 

topic/k2c-qli-build-ga/build_from_source_github.rst

@@ -19,7 +19,7 @@ Install and configure the required software tools on the Ubuntu host computer.
          pipx ensurepath
          pipx install kas
 
-#. Optionally download the kas-container script. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated evironment, consider using kas-container instead.
+#. Optionally download the kas-container script. The kas package also provides a kas-container script for running kas in a container. If you prefer running the image builds in an isolated environment, consider using kas-container instead.
 
    .. container:: nohighlight
 

topic/k2c-qli-build-ga/build_with_firmware.rst

@@ -450,19 +450,19 @@ Build firmware
 
          .. rubric:: CPUCP firmware
 
-         The CPUCP firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the CPUCP firmware as a binary and you don't need to compile the build.
 
          .. rubric:: CPUSYS.VM firmware
 
-         The CPUSYS.VM firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the CPUSYS.VM firmware as a binary and you don't need to compile the build.
 
          .. rubric:: BTFM firmware
 
-         The BTFM firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the BTFM firmware as a binary and you don't need to compile the build.
 
          .. rubric:: WLAN firmware
 
-         The WLAN firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the WLAN firmware as a binary and you don't need to compile the build.
 
          .. rubric:: Generate firmware prebuilds (boot-critical and split-firmware binaries)
 
@@ -740,19 +740,19 @@ Build firmware
 
          .. rubric:: CPUCP firmware
 
-         The CPUCP firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the CPUCP firmware as a binary and you don't need to compile the build.
 
          .. rubric:: CPUSYS.VM firmware
 
-         The CPUSYS.VM firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the CPUSYS.VM firmware as a binary and you don't need to compile the build.
 
          .. rubric:: BTFM firmware
 
-         The BTFM firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the BTFM firmware as a binary and you don't need to compile the build.
 
          .. rubric:: WLAN firmware
 
-         The WLAN firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the WLAN firmware as a binary and you don't need to compile the build.
 
          .. rubric:: Generate firmware prebuilds (boot-critical and split-firmware binaries)
 
@@ -767,7 +767,7 @@ Build firmware
                 cd <FIRMWARE_ROOT>/qualcomm-linux-spf-1-0_ap_standard_oem_nm/QCS9100.LE.1.0/common/build
                 python build.py --imf
 
-         - Firmware prebuild is successful if the following zip files are generated in the ``<FIRMWARE_ROOT>/qualcomm-linux-spf-1-0_ap_standard_oem_nm/QCM6490.LE.1.0/common/build/ufs/bin`` directory:
+         - Firmware prebuild is successful if the following zip files are generated in the ``<FIRMWARE_ROOT>/qualcomm-linux-spf-1-0_ap_standard_oem_nm/QCS9100.LE.1.0/common/build/ufs/bin`` directory:
 
             -  ``QCS9100_bootbinaries.zip``
             -  ``QCS9100_dspso.zip``
@@ -1030,19 +1030,19 @@ Build firmware
 
          .. rubric:: CPUCP firmware
 
-         The CPUCP firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the CPUCP firmware as a binary and you don't need to compile the build.
 
          .. rubric:: CPUSYS.VM firmware
 
-         The CPUSYS.VM firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the CPUSYS.VM firmware as a binary and you don't need to compile the build.
 
          .. rubric:: BTFM firmware
 
-         The BTFM firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the BTFM firmware as a binary and you don't need to compile the build.
 
          .. rubric:: WLAN firmware
 
-         The WLAN firmware is released as a binary and build compilation isn't required.
+         Qualcomm releases the WLAN firmware as a binary and you don't need to compile the build.
 
          .. rubric:: Generate firmware prebuilds (boot-critical and split-firmware binaries)