Boot attack clarification.

Signed-off-by: NicholasWoodIMG <142398143+NicholasWoodIMG@users.noreply.github.com>

specification/src/chapter2.adoc

@@ -477,10 +477,12 @@ Logical or physical
 a| * Glitching to bypass secure boot
 * Retrieving residual confidential memory after a system reset
 a| Implement robust power management, and adopt glitch-safe software techniques. +
+ +
 Industry best practice should be followed. For example: ensuring un-initialized variables are not used; implementing integrity checking of critical data and hardware provisioned parameters; implementing redundancy in encoding, verification, branching, and critical logic. +
  +
 Adopt randomization techniques between boot sessions. +
-For example: cryptographic memory protection with at least boot freshness; register ranomization. 
+ + 
+For example: cryptographic memory protection with at least boot freshness; register randomization. 
 
 | SR_PHY_004
 | Subverting supply chains