Update README.md

README.md

@@ -109,7 +109,7 @@ STM32WB is a multi-cores device even if the second core is not accessible by end
 CMSIS consists of three main components:
 
 * Family-specific headers, e.g. `stm32f4xx.h`
-* Cortex peripheral access layer header and source, e.g. `system_stm32f4xx.[c|h]`
+* Peripheral access layer header and source, e.g. `system_stm32f4xx.[c|h]`
 * Device type-specific startup sources (e.g. `startup_stm32f407xx.s`) (if ASM language is enabled)
 * Device-specific linker scripts which requires information about memory sizes (if ASM language is enabled)
 
@@ -124,7 +124,7 @@ That will add include directories, coretx peripheral layere files, startup sourc
 CMSIS creates the following targets:
 
 * `CMSIS::STM32::<FAMILY>` (e.g. `CMSIS::STM32::F4`) - common includes, compiler flags and defines for family
-* `CMSIS::STM32::<TYPE>` (e.g. `CMSIS::STM32::F407xx`) - common startup source for device type and cortex peripheral access layer files, depends on `CMSIS::STM32::<FAMILY>`
+* `CMSIS::STM32::<TYPE>` (e.g. `CMSIS::STM32::F407xx`) - common startup source for device type and peripheral access layer files, depends on `CMSIS::STM32::<FAMILY>`
 * `CMSIS::STM32::<DEVICE>` (e.g. `CMSIS::STM32::F407VG`) - linker script for device, depends on `CMSIS::STM32::<TYPE>`
 
 So, if you don't need linker script, you can link only `CMSIS::STM32::<TYPE>` library and provide your own script using `stm32_add_linker_script` function