Commit b0b450ab authored by Emanuele Aina's avatar Emanuele Aina

multiuser: Fix internal link

Signed-off-by: Emanuele Aina's avatarEmanuele Aina <>
parent ff893fa5
......@@ -206,7 +206,7 @@ multi-user systems.
available before, during and after any transition between users. The
set of core functionality could vary by device; in this document we
mainly use music playing and navigation as examples of this
category. See [][Preserving core functionality across user switching]
category. See [][Preserving “core” functionality across user-switching]
for further discussion of this topic.
- The subset of features that are not disturbed while switching
......@@ -214,7 +214,7 @@ multi-user systems.
considered to be “part of the operating system”. For example, it
should be possible to place a user-installable player for a
third-party music streaming service such as Spotify or in
this category. Again, see [][Preserving core functionality across user switching].
this category. Again, see [][Preserving “core” functionality across user-switching].
- Depending on the specific set of requirements, peripheral hardware
devices such as USB storage devices and paired Bluetooth devices
......@@ -1390,7 +1390,7 @@ concurrency, or if this is not acceptable, opt to leave user-switching
unsupported; for premium models with more capable hardware, the more
resource-expensive “fast user switching” approach can be considered.
In [][Preserving core functionality across user switching]
In [][Preserving “core” functionality across user-switching]
we outline various possible approaches to ensuring that
“core functionality” is not interrupted by a user switch. Services
that need to stay running after a user switch should have their
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment