aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDario Nieuwenhuis <[email protected]>2021-12-30 07:58:26 +0100
committerGitHub <[email protected]>2021-12-30 07:58:26 +0100
commitecb09b7313fa88fb02ac88f39acef0ee555ccd49 (patch)
treefcef104db901896ae849b2a515ddd6597558e5f3
parent7561fa19348530ce85e2645e0be8801b9b2bbe13 (diff)
parent5d86228077e72062ebb59e0300e81e92ffc54721 (diff)
Merge pull request #562 from tafia/patch-1
Update stm32.adoc
-rw-r--r--docs/modules/ROOT/pages/stm32.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/modules/ROOT/pages/stm32.adoc b/docs/modules/ROOT/pages/stm32.adoc
index 3d1fbfc8f..8ed9ab04b 100644
--- a/docs/modules/ROOT/pages/stm32.adoc
+++ b/docs/modules/ROOT/pages/stm32.adoc
@@ -11,7 +11,7 @@ code-generated register types that are identical for STM32 families with the sam
11 11
12=== The metapac 12=== The metapac
13 13
14The `stm32-metapac` module uses pre-generated chip and register definitions for STM32 chip families to generate register types. This is done at compile time based on Cargo feataure flags. 14The `stm32-metapac` module uses pre-generated chip and register definitions for STM32 chip families to generate register types. This is done at compile time based on Cargo feature flags.
15 15
16The chip and register definitions are located in a separate module, `stm32-data`, which is modified whenever a bug is found in the definitions, or when adding support for new chip families. 16The chip and register definitions are located in a separate module, `stm32-data`, which is modified whenever a bug is found in the definitions, or when adding support for new chip families.
17 17