From 1482a251867bfb31708e8c7273db4bee1e67df36 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Henrik=20Tj=C3=A4der?= <henrik@tjaders.com>
Date: Fri, 2 Oct 2020 09:55:25 +0000
Subject: [PATCH] Describe the resource struct attribute migration steps

---
 book/en/src/migration.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/book/en/src/migration.md b/book/en/src/migration.md
index ab45c29508..7be30943c8 100644
--- a/book/en/src/migration.md
+++ b/book/en/src/migration.md
@@ -66,6 +66,37 @@ mod app {
 }
 ```
 
+### Resources struct - #[resources]
+
+Previously the RTIC resources had to be in in a struct named exactly "Resources":
+
+``` rust
+struct Resources {
+    // Resources defined in here
+}
+```
+
+With RTIC v0.6.0 the resources struct is annotated similarly like
+`#[task]`, `#[init]`, `#[idle]`: with an attribute `#[resources]`
+
+``` rust
+#[resources]
+struct Resources {
+    // Resources defined in here
+}
+```
+
+In fact, the name of the struct is now up to the developer:
+
+``` rust
+#[resources]
+struct whateveryouwant {
+    // Resources defined in here
+}
+```
+
+would work equally well.
+
 ## Migrating from v0.4.x to v0.5.0
 
 This section covers how to upgrade an application written against RTIC v0.4.x to