diff --git a/deployment/volumes/README.md b/deployment/volumes/README.md
index 10f0fd226..1d849682c 100644
--- a/deployment/volumes/README.md
+++ b/deployment/volumes/README.md
@@ -3,14 +3,14 @@
 At the moment, the application needs two persistent volumes:
 
 * The `/data/` folder where `neo4j` stores its database and
-* the folder `/develop-backend/public/uploads` where the backend stores uploads.
+* the folder `/develop-backend/public/uploads` where the backend stores uploads, in case you don't use Digital Ocean Spaces (an AWS S3 bucket) for this purpose.
 
 As a matter of precaution, the persistent volume claims that setup these volumes
 live in a separate folder. You don't want to accidently loose all your data in
 your database by running
 
 ```sh
-kubectl delete -f human-connection/
+kubectl delete -f ocelot-social/
 ```
 
 or do you?
@@ -18,6 +18,7 @@ or do you?
 ## Create Persistent Volume Claims
 
 Run the following:
+
 ```sh
 # in folder deployments/
 $ kubectl apply -f volumes
@@ -25,7 +26,7 @@ persistentvolumeclaim/neo4j-data-claim created
 persistentvolumeclaim/uploads-claim created 
 ```
 
-## Backup and Restore
+## Backup And Restore
 
 We tested a couple of options how to do disaster recovery in kubernetes. First,
 there is the [offline backup strategy](./neo4j-offline-backup/README.md) of the