format line wrapping and fix escaped characters

1 files changed, 23 insertions, 26 deletions

diff --git a/content/blog/2024-02-13-ubuntu-emergency-mode.md b/content/blog/2024-02-13-ubuntu-emergency-mode.md
index 7482dd1..4b41406 100644
--- a/content/blog/2024-02-13-ubuntu-emergency-mode.md
+++ b/content/blog/2024-02-13-ubuntu-emergency-mode.md
@@ -7,12 +7,12 @@ draft = false
 
 # The Problem
 
-I recently [migrated my hard drives to a ZFS pool](../zfs/) and found
-myself stuck in Ubuntu\'s emergency mode after the first reboot I
-performed after creating the ZFS pool.
+I recently [migrated my hard drives to a ZFS pool](../zfs/) and found myself
+stuck in Ubuntu's emergency mode after the first reboot I performed after
+creating the ZFS pool.
 
-My server was stuck in the boot process and showed the following error
-on the screen:
+My server was stuck in the boot process and showed the following error on the
+screen:
 
 ``` txt
 You are in emergency mode.
@@ -21,34 +21,33 @@ After logging in, type "journalctl -xb" to view system logs,
 or ^D to try again to boot into default mode".
 ```
 
-After rebooting the server and watching the logs scroll on a monitor, I
-noticed the root cause was related to a very long search for certain
-drives. I kept seeing errors like this:
+After rebooting the server and watching the logs scroll on a monitor, I noticed
+the root cause was related to a very long search for certain drives. I kept
+seeing errors like this:
 
 ``` txt
 [ TIME ] Timed out waiting of device dev-disk-by/[disk-uuid]
 ```
 
-I realized that I had not removed the `/etc/fstab` references
-that asked Ubuntu to mount two disks on boot, but I had recently changed
-those disks to be part of my ZFS pool instead. Therefore, Ubuntu was
-trying to identify and mount a disk that was not available.
+I realized that I had not removed the `/etc/fstab` references that asked Ubuntu
+to mount two disks on boot, but I had recently changed those disks to be part of
+my ZFS pool instead. Therefore, Ubuntu was trying to identify and mount a disk
+that was not available.
 
-Now that we have an idea of the issue, let\'s move to solution.
+Now that we have an idea of the issue, let's move to solution.
 
 # The Solution
 
-In order to fix the issue, I waited until I was allowed to type the root
-user\'s password, and then I executed the following command:
+In order to fix the issue, I waited until I was allowed to type the root user's
+password, and then I executed the following command:
 
 ```sh
 nano /etc/fstab
 ```
 
-Within the `fstab` file, I needed to comment/remove the
-following lines at the bottom of the file. You can comment-out a line by
-prepending a `#` symbol at the beginning of the line. You can
-also delete the line entirely.
+Within the `fstab` file, I needed to comment/remove the following lines at the
+bottom of the file. You can comment-out a line by prepending a `#` symbol at the
+beginning of the line. You can also delete the line entirely.
 
 ``` conf
 # What it looked like when running into the issue:
@@ -60,16 +59,14 @@ UUID=E69867E59867B32B /mnt/white-02 ntfs-3g uid=1000,gid=1000 0 0
 # UUID=E69867E59867B32B /mnt/white-02 ntfs-3g uid=1000,gid=1000 0 0
 ```
 
-Once removing the lines above from the `/etc/fstab` file,
-save and exit the file by hitting the `Ctrl` + `x`
-key combo.
+Once removing the lines above from the `/etc/fstab` file, save and exit the file
+by hitting the `Ctrl` + `x` key combo.
 
-You can now hit `Ctrl` + `D` to continue, or
-reboot:
+You can now hit `Ctrl` + `D` to continue, or reboot:
 
 ```sh
 systemctl reboot
 ```
 
-Once rebooted, I was able to watch the machine boot properly and launch
-to the TTY login screen without errors!
+Once rebooted, I was able to watch the machine boot properly and launch to the
+TTY login screen without errors!