docs/Security:Add references to second stage bootloader to avoid confusion bettwen

bootloader and 2nd stage bootloader

docs/en/security/flash-encryption.rst

@@ -36,7 +36,7 @@ Encrypted Partitions
 
 With flash encryption enabled, the following types of data are encrypted by default:
 
-- Firmware bootloader
+- :ref:`second-stage-bootloader` (Firmware Bootloader)
 - Partition Table
 - :ref:`nvs_encr_key_partition`
 - Otadata

docs/en/security/host-based-security-workflows.rst

@@ -18,7 +18,7 @@ Goals
 #. Simplify the traditional workflow with stepwise instructions.
 #. Design a more flexible workflow as compared to the traditional firmware based workflow.
 #. Improve reliability by dividing the workflow in small operations.
-#. Eliminate dependency on firmware bootloader.
+#. Eliminate dependency on :ref:`second-stage-bootloader` (firmware bootloader).
 
 Pre-requisite
 -------------

docs/en/security/secure-boot-v2.rst

@@ -27,7 +27,7 @@ Secure Boot V2
 
         For ESP32 before ECO3, refer to :doc:`Secure Boot <secure-boot-v1>`. It is recommended that users use Secure Boot V2 if they have a chip version that supports it. Secure Boot V2 is safer and more flexible than Secure Boot V1.
 
-    Secure Boot V2 uses {IDF_TARGET_SBV2_SCHEME} based app and bootloader verification. This document can also be used as a reference for signing apps using the {IDF_TARGET_SBV2_SCHEME} scheme without signing the bootloader.
+    Secure Boot V2 uses {IDF_TARGET_SBV2_SCHEME} based app and bootloader (:ref:`second-stage-bootloader`) verification. This document can also be used as a reference for signing apps using the {IDF_TARGET_SBV2_SCHEME} scheme without signing the bootloader.
 
 .. only:: esp32