diff --git a/data/part-4/3-GitOps.md b/data/part-4/3-GitOps.md
index fa5a3d0c1..288aff294 100644
--- a/data/part-4/3-GitOps.md
+++ b/data/part-4/3-GitOps.md
@@ -386,10 +386,10 @@ There are a few options for the GitOps setup. What we used here was having the c
   Move the Project to use GitOps.
 
   - Create two separate environments, _production_ and _staging_ that are in their own namespaces
-  - In staging the resource limits are stricter compared to production and only one replica of each service is run
   - Each commit to the main branch should result in deployment to the staging environment
   - Each _tagged_ commit results in deployment to the production environment
   - In staging the broadcaster just logs all the messages, it does not forward those to any external service
+  - In staging database is not backed up
   - You may assume that _secrets_ are readily applied outside of the ArgoCD
   - Bonus: use different repositories for the code and configurations