diff --git a/source/chapter1-about.rst b/source/chapter1-about.rst
index cfaab94fd7421502ab713943d6adbd192f7cdbef..26a85cd9d3e6adbae9a21d3f8b5270e5daec797c 100644
--- a/source/chapter1-about.rst
+++ b/source/chapter1-about.rst
@@ -60,11 +60,11 @@ without UEFI is outside the scope of this document.
 - The first stage bootloader **must** be able to access our firmware NVCounter.
 - UEFI capsule updates are the mechanism used for delivering firmware updates. 
   Refer to [#UEFICapsuleUpdateNote]_ for details.
-- We assume that the masked ROM can load the first staged boot loader (e.g TF-A) from a dual image.
+- We assume that our immutable stage loader can load the second stage boot loader (e.g TF-A) from a dual image.
   In case the masked ROM can not boot with an alternative location, similar functionality
-  can be added to the secondary bootloader stage.
-  In that case updating the Secondary bootloader stage should be disallowed from OTA
-  update.  In person update of Secondary bootloader stage may be possible and may require extra
+  **must** be added to the secondary bootloader stage.
+  In that case updating the secondary bootloader stage should be disallowed from OTA
+  update.  In person update of secondary bootloader stage may be possible and may require extra
   tools or procedures but that is out of the scope of this document.
 - Update process can target a single firmware component or multiple components.  Updating multiple
   components and multiplexing boot combinations can be very challenging.  In this document we treat