diff --git a/docs/user/troubleshooting/plasma.md b/docs/user/troubleshooting/plasma.md
index 8fb0d63f7..bb343c3d2 100644
--- a/docs/user/troubleshooting/plasma.md
+++ b/docs/user/troubleshooting/plasma.md
@@ -19,13 +19,12 @@ This is often caused by a Firefox bug. It can be triggered by various things, li
 You may not need to reboot to recover from this state. Killing all firefox processes may be all that's necessary. To do so:
 
 1. Open a virtual terminal by pressing `Ctrl+Alt+F3`.
-2. Run the following to kill all firefox windows:
+1. Run the following to kill all firefox windows:
   ```bash
   killall firefox
   ```
   This should close all Firefox windows.
-3. Return to the Plasma session by pressing `Ctrl-Alt-F2`.
-
+1. Return to the Plasma session by pressing `Ctrl-Alt-F2`.
   You should now be able to use Plasma normally.
 
 ## Application windows look corrupt / incomplete
@@ -43,43 +42,32 @@ You should not be logged into your Plasma session while doing this. It is also h
 :::
 
 1. While still logged into your Plasma session, cd to your home directory:
-
   ```bash
   cd
   ```
-
-2. Run these commands to back up the following directories:
-
+1. Run these commands to back up the following directories:
   ```bash
   cp -av ~/.kde{,.bak}
   cp -av ~/.config{,.bak}
   cp -av ~/.local{,.bak}
   cp -av ~/share{,.bak}
   ```
-
   The output will show what files were copied. Each directory will have another copy with a .bak extension such as `~/.config.bak`. These can be used to recover configuration files, if necessary.
-
-2. Shut down the system. Boot from a live USB, such as one of the Solus live environments.
-3. Mount your hard drive's system. For instructions on how to do this see [Mounting your system](/docs/user/troubleshooting/boot-rescue#mounting-your-system).
-4. Change to your user's directory where you mounted your system. In this example, your system has been mounted to `/mount`:
-
+1. Shut down the system.
+1. Boot from a live USB, which you can create from one of the [Solus installers](https://getsol.us/download/).
+2. [Mount your hard drive's file system](./boot-rescue.md#mounting-your-system).
+3. Change to your user's directory where you mounted your system. In this example, your system has been mounted to `/mount`:
   ```bash
   cd /mount/home/username
   ```
-
   Replace "username" with the username you use for Solus.
   You can make sure the directory is correct by listing the files:
-
   ```bash
   ls -laH
   ```
-
   You should see the files you would usually see in your home directory when logged into Solus normally.
-
-5. Now you need to remove the various caches that Plasma uses.
-
-  Run the following from your home directory that you just switched to:
-
+1. Now you need to remove the various caches that Plasma uses.
+  Execute the following commands:
   ```bash
   rm -rf .kde
   rm -rf .cache/plasmashell*
@@ -97,10 +85,9 @@ You should not be logged into your Plasma session while doing this. It is also h
   rm -f plasma*
   rm -rf kde* akonadi* KDE kconf_updaterc baloo* dolphinrc drkonqirc gwenviewrc kmail2rc k*rc katemetainfos
   ```
-6. Shut down the live environment and remove the live USB drive.
-7. Reboot back into your regular Plasma session. Check the application to see if it looks OK now.
-8. It should not be necessary to recover the cache files that were deleted. If you need to, you can recover a file by copying it from the backup directory to the actual directory.
-
+1. Shut down the live environment and remove the live USB drive.
+1. Reboot back into your regular Plasma session. Check the application to see if it looks OK now.
+1. It should not be necessary to recover the cache files that were deleted. If you need to, you can recover a file or directory by copying it from the backup directory to the actual directory.
   For example, to recover the file `.kde/share/config/kdeglobals`:
   ```
   cp -av .kde.bak/share/config/kdeglobals .kde/share/config/kdeglobals