markdown syntax: formatted all files with prettier

wiki/linux/disk-management.md

@@ -2,16 +2,21 @@
 
 ## Grow non-LVM ext4 partition
 
-ATTENTION: Please note that the partition to enlarge has to be the last one with the free space after it.
+ATTENTION: Please note that the partition to enlarge has to be the last one with
+the free space after it.
 
 SSH into the VM.
+
 - run `lsblk` check if the disk size has changed
 - if not `reboot` the virtual machine
 
 In the following it is assumed that the partition to enlarge is `/dev/sda2`
+
 - change the size of the partition with `parted /dev/sda`
-- inside of parted run `print free` and check where the free space after your partition ends
-- run `resizepart` and follow the instructions; End is the number you checked in the last step
+- inside of parted run `print free` and check where the free space after your
+partition ends
+- run `resizepart` and follow the instructions; End is the number you checked in
+the last step
 - `quit` parted
 
 Now you need to resize the filesystem with `resize2fs /dev/sda2`.
@@ -22,10 +27,12 @@ Now you need to resize the filesystem with `resize2fs /dev/sda2`.
 
 source: [https://askubuntu.com/questions/197459/how-to-fix-sudo-unable-to-open-read-only-file-system]
 
-Ususally the filesystem will go into read-only mode whe the system is running and there is a consistency error.
+Ususally the filesystem will go into read-only mode whe the system is running
+and there is a consistency error.
 To fix it run:
+
 - `sudo fsck -Af -M` - check all filesystems
-If `fsck` gets stuck after its version banner:
-`fsck from util-linux 2.20.1`
-you may want to try using the ext4-specific fsck:
+  If `fsck` gets stuck after its version banner:
+  `fsck from util-linux 2.20.1`
+  you may want to try using the ext4-specific fsck:
 - `fsck.ext4 -f /dev/sda1`