Fix Liquid

Author: dshevtsov

guides/v2.2/cloud/env/variables-deploy.md

@@ -115,7 +115,7 @@ Configure how consumers process messages from the message queue by choosing one
 
 - `true`—Consumers continue to process messages from the message queue until reaching the maximum number of messages (`max_messages`) specified in the `CRON_CONSUMERS_RUNNER` deploy variable before closing the TCP connection and terminating the consumer process. If the queue empties before reaching `max_messages`, the consumer waits for more messages to arrive.
 
-{: .bs-callout .bs-callout-warning}
+{: .bs-callout .bs-callout-warning }
 If you use workers to run consumers instead of using a cron job, set this variable to true.
 
 ```yaml
@@ -129,7 +129,7 @@ stage:
 -  **Default**—_Not set_
 -  **Version**—Magento 2.1.4 and later
 
-{{ .bs-callout-warning }}
+{: .bs-callout-warning }
 You must set the `CRYPT_KEY` value through the Project Web UI instead of the `.magento.env.yaml` file to avoid exposing the key in the source code repository for your environment. See [Set environment and project variables]({{ page.baseurl }}/cloud/project/project-webint-basic.html#project-conf-env-var).
 
 When you move the database from one environment to another without an installation process, you need the corresponding cryptographic information. Magento uses the encryption key value set in the Web UI as the `crypt/key` value in the `env.php` file. This does not overwrite an existing encryption key value in the `env.php` file.