diff --git a/2-farm/lessons/4-migrate-your-plant-to-the-cloud/README.md b/2-farm/lessons/4-migrate-your-plant-to-the-cloud/README.md
index a8b182b2..4be631e3 100644
--- a/2-farm/lessons/4-migrate-your-plant-to-the-cloud/README.md
+++ b/2-farm/lessons/4-migrate-your-plant-to-the-cloud/README.md
@@ -102,7 +102,7 @@ The public test MQTT broker you have been using is a great tool when learning, b
 * Performance - it is designed for only a few test messages, so wouldn't cope with a large amount of messages being sent
 * Discovery - there is no way to know what devices are connected
 
-IoT services in the cloud solve these problems. They are maintained by large cloud providers who invest heavily in reliability and are on hand to fix any issues that might arise. They have security baked in to stop hackers reading your data or sending rogue commands. They are also high performance, being able to handle many millions of messages every day, taking advantage of the cloud to scale as needed.
+IoT services in the cloud solve these problems. They are maintained by large cloud providers who invest heavily in reliability and are on hand to fix any issues that might arise. They have security baked-in to stop hackers reading your data or sending rogue commands. They are also high performance, being able to handle many millions of messages every day, taking advantage of the cloud to scale as needed.
 
 > 💁 Although you pay for these upsides with a monthly fee, most cloud providers offer a free version of their IoT service with a limited amount of messages per day or devices that can connect. This free version is usually more than enough for a developer to learn about the service. In this lesson you will be using a free version.