Update readme

README.md

@@ -57,7 +57,7 @@ also available for each unmanaged host in `docs/hosts`.
 ## Data storage guidance
 There are three categories of data used by applications, each should be
 stored in their own specific way to ensure minimal possibility of data loss.
-**Nothing should be deployed if it doesn't follow these guidelines!**
+**Nothing should be deployed if it doesn't follow these guidelines**!
 
 **Runtime state:** Data that has to be persisted to disk, but is not required
 to be present after a restart of the application. Things such as encoding caches
@@ -68,7 +68,7 @@ only**.
 between restarts, but can be easily replaced if it is lost. This is things such
 as SSL certificates for traefik, as re-requesting these might cause
 rate-limiting related issues. **This data should be persisted to the 
-`/persistent` directory. Use nix-impermanence for this.**.
+`/persistent` directory. Use nix-impermanence for this**.
 
 **Application/user data:** This is most data managed by the system. This is data
 that can not easily be replaced, such as pictures, videos, and other user
@@ -77,14 +77,15 @@ Immich's database. **This data should be persisted to the Ceph cluster.
 Preferably in real-time, but if this is infeasible, for example, running
 databases on top of ceph incurs a large performance hit, the data should be 
 persisted in an automated fashion, such as through a cron job making a backup
-every x hours.**
+every x hours**.
 
 
 ## TODO:
+- Write automation to notify me of outdated docker images in `dockerImages.nix`.
+- Automatic backup of postgres data (yes, I know this should have been done before deploying).
 
 ### Services
 **For sure**:
-- FreshRSS: RSS server/reader
 - Gramps: Family tree
 - hoarder: Bookmark manager
 - immich: Photos