summaryrefslogtreecommitdiff
path: root/src/soc/intel/broadwell/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'src/soc/intel/broadwell/Kconfig')
-rw-r--r--src/soc/intel/broadwell/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/soc/intel/broadwell/Kconfig b/src/soc/intel/broadwell/Kconfig
index fbd7aea26b..f02e810b23 100644
--- a/src/soc/intel/broadwell/Kconfig
+++ b/src/soc/intel/broadwell/Kconfig
@@ -23,7 +23,7 @@ config BROADWELL_VBOOT_IN_BOOTBLOCK
Broadwell can either start verstage in a separate stage
right after the bootblock has run or it can start it
after romstage for compatibility reasons.
- Broadwell however uses a mrc.bin to initialse memory which
+ Broadwell however uses a mrc.bin to initialize memory which
needs to be located at a fixed offset. Therefore even with
a separate verstage starting after the bootblock that same
binary is used meaning a jump is made from RW to the RO region