diff --git a/docs/ca/dev/environment-scaling.md b/docs/ca/dev/environment-scaling.md
index 34961fe6cf5..ad850160fad 100644
--- a/docs/ca/dev/environment-scaling.md
+++ b/docs/ca/dev/environment-scaling.md
@@ -7,7 +7,7 @@ template: concept-topic-template
 
 Production environments, unlike staging environments, are equipped with auto-scaling capabilities. This enables the resources used by the application to dynamically scale up or down based on the current load. This document uses the checkout analogy as an example to explain the types of scaling.
 
-## General Considerations
+## General considerations
 
 * While all production environments offer some form of automatic scaling by default, environments must be optimized for your work load. To do it, schedule a load test by creating a "Announce High Load/Traffic" case at the [support portal](https://support.spryker.com). Plan for at least three days of lead time.
 * Load tests are usually performed in rounds. After deploying a typical infrastructure configuration for the size of your project, we'll ask you to perform load testing. The results are analyzed and the environment is dialed in. This pattern is repeated until the environment is configured to support the expected load. For a good result, two to three rounds are needed.