diff --git a/docs/reference/administration/reviewing-classic-confinement-snaps.md b/docs/reference/administration/reviewing-classic-confinement-snaps.md index 041ac317..b2fd74fa 100644 --- a/docs/reference/administration/reviewing-classic-confinement-snaps.md +++ b/docs/reference/administration/reviewing-classic-confinement-snaps.md @@ -56,7 +56,7 @@ Classic requests generally fall under a number of categories. Below lists catego * hard-coded paths (use snapcraft-preload, layouts) * ability to run other snaps directly (as opposed to defined interfaces) * access to arbitrary files on the system because the application isn't designed with confinement in mind (if a desktop application, use portals or [xdg-open](https://forum.snapcraft.io/t/allowing-xdg-open-to-open-files/3789/11)) -* access to arbitrary files on the system due to developer/user inertia (home and removable-media is almost always sufficient, though {ref}`personal-files ` and {ref}`system-files ` may be used under certain circumstances. +* access to arbitrary files on the system due to developer/user inertia ({ref}`home ` and {ref}`removable-media ` is almost always sufficient, though {ref}`personal-files ` and {ref}`system-files ` may be used under certain circumstances) * access to arbitrary files on the system to avoid increasing a snap's size * [GNOME shell extensions](https://forum.snapcraft.io/t/yaru-dark-theme-toggle-review-request/13169/7) * [nautilus extensions](https://forum.snapcraft.io/t/synchrorep-need-classic-confinement/13347/8)