diff --git a/docs/ca/dev/environment-scaling.md b/docs/ca/dev/environment-scaling.md
index d1f9c8f9aa..b26e7a84f4 100644
--- a/docs/ca/dev/environment-scaling.md
+++ b/docs/ca/dev/environment-scaling.md
@@ -7,6 +7,12 @@ 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.
 
+{% info_block infoBox "" %}
+* 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.
+* We don't recomment load testing in live production environments because this can affect the experience of your visitors. Instead, book a production-like environment or upgrade one of your non-production environments to perform the tests.
+{% endinfo_block %}
+
 ## Cloud architecture
 
 EC2 hosts are used to deploy Docker containers. One host generally has multiple containers running with Spryker services, such as Yves and BackGW. The containers may only reserve up to the configured amount of CPU and RAM of the host machine. Additional hosts, up to a configured maximum number of hosts, are deployed as needed so that more containers can be placed on them in scaling events.
diff --git a/docs/ca/devscu/configure-spryker-code-upgrader.md b/docs/ca/devscu/configure-spryker-code-upgrader.md
index 7d95c00109..12392a9d0e 100644
--- a/docs/ca/devscu/configure-spryker-code-upgrader.md
+++ b/docs/ca/devscu/configure-spryker-code-upgrader.md
@@ -26,6 +26,12 @@ To configure the Upgrader, follow the steps:
 
 5. On the **Run: #1** page, update the needed parameters and click **Proceed**.
 
+{% info_block infoBox %}
+
+JSON values must be added in one line and without whitespaces.
+
+{% endinfo_block %}
+
 ![Spryker CI Set Config Upgrader Pipeline](https://spryker.s3.eu-central-1.amazonaws.com/docs/paas%2B/dev/configure-spryker-code-upgrader.md/set-spryker-code-upgrader-variables.png)
 
 This runs the pipeline. After it finishes, the configuration gets updated.