Add more markdown newlines

README.md

@@ -5,10 +5,14 @@
 **Create symbolic links given a custom set of commands**
 
 Mainly created out of frustration of windows ""symbolic"" links
+
 This tool creates real symbolic links on any platform following the syntax of:
 `source,destination,force?`
+
 It respects existing files (be them real files or symbolic links)
+
 Unless force is set to *t* in which case only existing symbolic links are deleted (overwriten)
+
 Real files will never be deleted by this tool
 
 The commands can be given by:
@@ -64,10 +68,15 @@ executable.exe
 ```
 
 The tool will not delete any files by overwriting existing ones
+
 And thanks to that it will fail when running on files that have already been renamed by it
+
 For such scenarios use `fiter -f <glob>`
+
 *-f* renames all files to \<file\>.bak before renaming them back to their new iterative name
+
 This means that it can run on files that already have iterative names because none are being overwriten
+
 **It also means that, on failure, files are left as .bak**
 
 ## [fmoditer](https://git.site.quack-lab.dev/dave/fmoditer)
@@ -93,7 +102,9 @@ Running `fmoditer *.mp4` would result in
 **"clean" vscode recent projects by deleting non existing entries and adding new folders**
 
 Reads given directories and adds all folders in directories to vscode's recent projects
+
 The idea is that all projects in a "projects" folder should be accessible to vscode
+
 Doing this manually requires opening every folder one by one
 
 It also removes non existent entries from recent projects and recent files
@@ -133,9 +144,13 @@ Usage of repo.exe:
 **Runs programs specified in *autoruns.json* (at compile time)**
 
 This tool is meant to replace windows autoruns and is meant to be magnitudes faster than windows autoruns
+
 note: autoruns is specifically embedded as to not have to drag *autoruns.json* across multiple directories
+
 It also supports automatically hiding/closing windows and running only programs that are not already running
+
 See sample *autoruns.json* in repository of the tool
+
 Supported json fields are:
 ```go
 Entry struct {
@@ -179,7 +194,9 @@ Runs
 It also sets its identity to *system system@localhost*
 
 The purpose of this tool is to make sure you never lose any data in a possibly volatile directory
+
 For example given a directory where it's possible for files to spontaneously combust
+
 This tool will ensure they're never really lost thanks to git
 
 ## [directory-cleaner](https://git.site.quack-lab.dev/dave/directory-cleaner)
@@ -187,6 +204,7 @@ This tool will ensure they're never really lost thanks to git
 Meant to run as a service - preferably in a docker container
 
 Meant to clean up "temporary" directories where the host program does not do a good job of deleting old entries, for example the windows temp
+
 Configuration is given through environmental variables:
 - *ROOT*
 	- Defaults to /tmp
@@ -212,16 +230,22 @@ Configuration is given through environmental variables:
 	- Use modtime instead of accesstime
 
 The tool uses access time to determine age of files with the thinking that files that should be deleted are ones that are not used
+
 It also supports using mod time instead
+
 This is important because moving files from *ROOT* to *ROOT_ARCHIVE* after *ARCHIVE_THRESHOLD* **resets their atime and mtime**
+
 ...because they're accessed and modified
+
 Therefore file time to live is actually *ARCHIVE_THRESHOLD* + *DELETE_THRESHOLD*
 
 ## [directory-deletor](https://git.site.quack-lab.dev/dave/directory-deletor)
 **Deletes given directories in a directory on a set interval**
 
 Very similar to *directory-cleaner* except that this tool straight out deletes given directories
+
 It's meant to combat windows unrelenting spam of "3D Projects" in ~
+
 Who even uses that folder? Why is it there? Why can't I delete it? Well, now you can
 
 Part of the configuration is done through command line arguments: