diff --git a/_posts/2018-02-15-data-recovery.markdown b/_posts/2018-02-15-data-recovery.markdown
index 0cec5a4..dd9f9a2 100644
--- a/_posts/2018-02-15-data-recovery.markdown
+++ b/_posts/2018-02-15-data-recovery.markdown
@@ -11,7 +11,8 @@ Suppose you are using macOS and your endangered disk is formatted with HFS+.
 
 ## Inspect
 Use `diskutil list` to verify that which drive is damaged.
-This article assumes that `disk2` is the damaged one AND a partition `disk2s2` is what you expected to be rescued. You don't want to save `disk2s1` that is usually EFI partition.
+
+This article assumes that `disk2` is the damaged AND a partition `disk2s2` is what you expected to be rescued. You don't want to save `disk2s1` that is usually EFI partition.
 
 ## Damage Control
 To prevent extra load, unmount the damaged disk: `diskutil unmountDisk disk2`.
@@ -25,7 +26,9 @@ sudo ddrescue -n -v /dev/disk2s2 ./hdimage.dmg ./mapfile
 ```
 
 So this command will start rescuing your data from `/dev/disk2s2` partition to `hdimage.dmg` while writing log to `mapfile`.
+
 You might want to rescue data as fast as possible. option `-n` is here for. This will skip scraping phase that causes aggressive disk access. 
+
 Option `-v` stand for verbose logging.
 
 ```bash
@@ -33,8 +36,11 @@ sudo ddrescue -r5 -v /dev/rdisk2s2 ./hdimage.dmg ./mapfile
 ```
 
 When the first command completed, do it again with different parameters to aggressively scrape bad area failed to access the first time.
+
 Option `-r5` means ddrescue will try rescuing damaged area for 5 times.
+
 And `/dev/disk2s2` become `/dev/__r__disk2s2` this time. `r` stand for raw so this will access the disk more direct way.
+
 > Beware: You MUST use same `hdimage.dmg` and `mapfile` between two commands. `mapfile` remembers which blocks were rescued and vise versa.
 
 # Aftercare