diff --git a/readme.md b/readme.md
index abcec8a..5fdf4ab 100644
--- a/readme.md
+++ b/readme.md
@@ -49,14 +49,11 @@ norg -c myconfig.toml extract pcname-2024-08-18T15:20:17773204
 norg -c myconfig.toml extract pcname-2024-08-18T15:20:17773204 --destination /tmp/my_extracted_archive
 ```
 
-## Work in Progress
-Norg is still very much a work in progress, so there will be bugs. Please raise 
-and issue, or create a pull request for any issues and resolutions you may have.
 
 ## Naming. Why "Norg"?
 Well, I don't know. I'm a Star Trek fan so obviously I wanted to keep something 
-in line with the [Borg pseudo-species](https://memory-alpha.fandom.com/wiki/Borg) as the borg backup utility does.
-Also, sometimes I feel my code has elements of inexperience but loads of potential... which reminded me of [Nog](https://memory-alpha.fandom.com/wiki/Nog)
+in line with the [Borg pseudo-species](https://memory-alpha.fandom.com/wiki/Borg) as the borg backup utility does.  
+Also, sometimes I feel my code has elements of inexperience but loads of potential... which reminded me of [Nog](https://memory-alpha.fandom.com/wiki/Nog).  
 So, simply put, `Norg` is an portmanteau of "Borg" and "Nog".
 
 ## Why create this when Borgmatic exists?
@@ -67,6 +64,10 @@ package repositories so ended up building it from source on all computers. This
 was a lengthy process, and borgmatic isn't very portable, so I wanted to make something that had to features I needed, in a single portable binary.  
 Norg was the outcome of this.  
 
+## Work in Progress
+Norg is still very much a work in progress, so there will be bugs. Please raise 
+and issue, or create a pull request for any issues and resolutions you may have.
+
 ## Contact
 For any issues, please raise an issue here. Otherwise, I can be contacted via 
 the fediverse at [@paul@notnull.space](https://notnull.space/@paul).