aboutsummaryrefslogtreecommitdiff
path: root/book/en/src/internals/access.md
diff options
context:
space:
mode:
Diffstat (limited to 'book/en/src/internals/access.md')
-rw-r--r--book/en/src/internals/access.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/book/en/src/internals/access.md b/book/en/src/internals/access.md
index a4c9ca0..6433707 100644
--- a/book/en/src/internals/access.md
+++ b/book/en/src/internals/access.md
@@ -1,6 +1,6 @@
# Access control
-One of the core foundations of RTFM is access control. Controlling which parts
+One of the core foundations of RTIC is access control. Controlling which parts
of the program can access which static variables is instrumental to enforcing
memory safety.
@@ -12,8 +12,8 @@ resides in the same scope in which they are declared. Modules give some control
over how a static variable can be accessed by they are not flexible enough.
To achieve the fine-grained access control where tasks can only access the
-static variables (resources) that they have specified in their RTFM attribute
-the RTFM framework performs a source code level transformation. This
+static variables (resources) that they have specified in their RTIC attribute
+the RTIC framework performs a source code level transformation. This
transformation consists of placing the resources (static variables) specified by
the user *inside* a `const` item and the user code *outside* the `const` item.
This makes it impossible for the user code to refer to these static variables.
@@ -28,7 +28,7 @@ The code below is an example of the kind of source level transformation that
happens behind the scenes:
``` rust
-#[rtfm::app(device = ..)]
+#[rtic::app(device = ..)]
const APP: () = {
static mut X: u64: 0;
static mut Y: bool: 0;