diff --git a/pages/docs/device-app/develop.mdx b/pages/docs/device-app/develop.mdx
index 70d1111c..af36d361 100644
--- a/pages/docs/device-app/develop.mdx
+++ b/pages/docs/device-app/develop.mdx
@@ -30,6 +30,6 @@ To get your project started quickly, we provide a complete framework made to dev
   - [A `Rust` Boilerplate](https://github.com/LedgerHQ/app-boilerplate-rust) and
   - [A Plugin Boilerplate](https://github.com/LedgerHQ/app-plugin-boilerplate)
 
-More information on these components can be found in the [tutorials](./tutorials), [development environment](./tutorials)
-and [tools](./tools) sections.
+More information on these components can be found in the [tutorials](./develop/tutorials), [development environment](./develop/tutorials#development-environment)
+and [tools](./develop/tools) sections.
 
diff --git a/pages/docs/device-app/develop/ui/ledger-nano-display/low-level-display-management.mdx b/pages/docs/device-app/develop/ui/ledger-nano-display/low-level-display-management.mdx
index 76a270ee..6de11d61 100755
--- a/pages/docs/device-app/develop/ui/ledger-nano-display/low-level-display-management.mdx
+++ b/pages/docs/device-app/develop/ui/ledger-nano-display/low-level-display-management.mdx
@@ -49,7 +49,7 @@ See [the sample apps](https://github.com/LedgerHQ/ledger-sample-apps) for exampl
 
 ## BOLOS UX
 
-The BOLOS UX is the implementation of the device-wide user interface; it is a component of the [dashboard application](../../../../architecture/bolos#dashboard). Applications delegate certain jobs to the BOLOS UX in order to retain consistency across all apps for certain UI components, as well as to allow the operating system to override the application's UI when necessary (for example, when locking the screen). The application interfaces with the BOLOS UX using `os_ux(...)`, which is a system call. However, applications don't need to call this function as it is automatically called by the display interaction helpers (the `UX_` macros).
+The BOLOS UX is the implementation of the device-wide user interface; it is a component of the [dashboard application](../../../architecture/bolos#the-dashboard). Applications delegate certain jobs to the BOLOS UX in order to retain consistency across all apps for certain UI components, as well as to allow the operating system to override the application's UI when necessary (for example, when locking the screen). The application interfaces with the BOLOS UX using `os_ux(...)`, which is a system call. However, applications don't need to call this function as it is automatically called by the display interaction helpers (the `UX_` macros).
 
 Applications should delegate **Events** like **Button Push Events** to the BOLOS UX (in this case, using `UX_BUTTON_PUSH_EVENT(...)`) instead of handling them directly, in case the BOLOS UX needs to override the application's UI. If the event is consumed by the BOLOS UX (for example, a pressed button while the user is unlocking the screen) then the event is not passed on to the application.