diff --git a/README.md b/README.md
index 39d16d5..c80b06e 100755
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ You have an environment that allows to run
 
 ### Build and test
 
-In the root directory, run `docker-compose up`.
+In the root directory, run `docker compose up`.
 
 
 
diff --git a/requirements/F/_posts/2000-01-19-fast-startup-time.md b/requirements/F/_posts/2000-01-19-fast-startup-time.md
index 2c5d4f9..8a3ab45 100755
--- a/requirements/F/_posts/2000-01-19-fast-startup-time.md
+++ b/requirements/F/_posts/2000-01-19-fast-startup-time.md
@@ -1,7 +1,7 @@
 ---
-title: "Fast startup time"
+title: "Fast startup time (less than 90 seconds)"
 tags: efficient
-related: time behaviour, speed, performance, startup-time 
+related: time behaviour, speed, performance, startup-time, elasticity 
 permalink: /requirements/fast-startup-time
 ---
 
diff --git a/requirements/S/_posts/2023-09-03-scale-up-in-2-minutes.md b/requirements/S/_posts/2023-09-03-scale-up-in-2-minutes.md
new file mode 100755
index 0000000..df4a279
--- /dev/null
+++ b/requirements/S/_posts/2023-09-03-scale-up-in-2-minutes.md
@@ -0,0 +1,27 @@
+---
+title: "Scale up in 2 Minutes"
+tags: efficient, reliable
+related: elasticity, scalability, performance
+permalink: /requirements/scale-up-in-2-minutes
+---
+
+<div class="quality-requirement" markdown="1">
+
+
+**Background**: A cloud-based web application, with a sudden increase in user traffic, such as during a promotional event or a major product launch. Auto-scaling features are available and configured.
+
+
+**Response**: The system automatically detects the increase in load and provisions additional resources to handle the increased traffic, without human intervention.
+
+**Metric**: 
+* Time to Scale: The system should begin scaling up additional resources within 2 minutes of detecting a 50% increase in traffic load.
+* Resource Utilization: After scaling, CPU and memory utilization should stabilize at approximately 70%, ensuring that resources are neither underutilized (wasteful) nor overburdened (which could degrade performance).
+* Performance Maintenance: The response time of the web application should not exceed 3 seconds for 95% of the requests, even during peak traffic.
+Cost Efficiency: The cost of scaled resources should not exceed a 150% increase despite a 200% increase in traffic, emphasizing cost-effective scaling.
+
+</div><br>
+
+This requirement was created with help from [ChatGPT](https://chat.openai.com) by using the prompt `create a quality attribute scenario to describe a elasticity requirement for a web application`.
+
+
+