refactor(docs): Layout (#1)

README.md

@@ -126,7 +126,7 @@ With these settings it is possible to cause ZFS snapshot name collisions (meanin
 - They cover the same type of operation (_Install_, _Remove_ or _Upgrade_)
 - They cover the same list of packages
 
-The script safeguards against naming collisions by adding a monotoniccally incrementing counter after the timestamp string.
+The script safeguards against naming collisions by adding a monotonically incrementing counter after the timestamp string.
 
 For example by running `pacman -S tmux` three times within the same minute (once for an _Install_ operation and two more times for two identical _Upgrade_ operations) your system may generate the following example snapshots:
 ```
@@ -138,7 +138,7 @@ zpool/root/archlinux@pacman_2023-03-07-0116_2_op:upgr_sev:trv_pkgs:tmux
 
 Notice that lines 2 and 3 would collide since their dataset names are virtually identical other than the counter suffix which was incremented by 1 to avoid a collision.
 
-> This facilitates a hands-off approach to using this script on a daily driver system without risking missing snapshots or employing other more involved approaches to avoid naming collisions.
+This facilitates a hands-off approach to using this script on a daily driver system without risking missing snapshots or employing other more involved approaches to avoid naming collisions.
 
 # Rollback