diff --git a/analytics/README.md b/analytics/README.md
new file mode 100644
index 0000000..86607cf
--- /dev/null
+++ b/analytics/README.md
@@ -0,0 +1,2 @@
+Placeholder for: 
+https://github.com/dwyl/learn-devops/issues/91
\ No newline at end of file
diff --git a/postgres/README.md b/postgres/README.md
index 4650e59..cc360fa 100644
--- a/postgres/README.md
+++ b/postgres/README.md
@@ -1,15 +1,26 @@
-# `Postgres` Setup
+<div align="center">
+
+<img width="400" src="https://github.com/user-attachments/assets/1e42af6e-6b71-4d63-b39a-a40e5344d913" 
+alt="Postgres logo wide" />
+
+# Deployment
+
+</div>
 
 `Postgres` deployment is divided into two options:
 
-1. Managed - the infrastructure provider manages the instances for you.
-2. Unmanaged - we the engineers or operations team need to manage it.
+1. Managed - the infrastructure provider manages the instances for you
+   including data backups and failover in the event of a crash/corruption.
+2. Unmanaged - we the engineers or operations team need to manage it
+   including data integrity and availability.
 
 Both have their place.
 But if you are not an _experienced_
 Database Administrator (DBA)
 or System Administrator (SysAdmin),
 you should seriously consider a _managed_ service.
+The risk of data loss greatly outweighs
+the cost of a _managed_ service.
 
 With that in mind we have prepared a quick guide
 to deploying _managed_ `Postgres` on `DigitalOcean`:
diff --git a/postgres/managed-postgres-digitalocean.md b/postgres/managed-postgres-digitalocean.md
index d48f187..e544b4a 100644
--- a/postgres/managed-postgres-digitalocean.md
+++ b/postgres/managed-postgres-digitalocean.md
@@ -63,9 +63,6 @@ Viewing this we realized that we needed to launch a Droplet (VPS) instance
 in order to secure the DB Cluster ...
 
 
-
-
-
 ## 4. Connect to Cluster