diff --git a/content/get-started/swarm-deploy.md b/content/get-started/swarm-deploy.md
index a6814d2901..1315c8da47 100644
--- a/content/get-started/swarm-deploy.md
+++ b/content/get-started/swarm-deploy.md
@@ -42,7 +42,15 @@ services:
 
 In this Swarm YAML file, we have just one object: a `service`, describing a scalable group of identical containers. In this case, you'll get just one container (the default), and that container will be based on your `getting-started` image created in [Part 2](02_our_app.md) of the Quickstart tutorial. In addition, We've asked Swarm to forward all traffic arriving at port 8000 on our development machine to port 3000 inside our getting-started container.
 
-> **Kubernetes Services and Swarm Services are very different!** Despite the similar name, the two orchestrators mean very different things by the term 'service'. In Swarm, a service provides both scheduling _and_ networking facilities, creating containers and providing tools for routing traffic to them. In Kubernetes, scheduling and networking are handled separately: _deployments_ (or other controllers) handle the scheduling of containers as pods, while _services_ are responsible only for adding networking features to those pods.
+> **Kubernetes Services and Swarm Services are very different!** 
+>
+> Despite the similar name, the two orchestrators mean very different things by
+> the term 'service'. In Swarm, a service provides both scheduling _and_
+> networking facilities, creating containers and providing tools for routing
+> traffic to them. In Kubernetes, scheduling and networking are handled
+> separately: _deployments_ (or other controllers) handle the scheduling of
+> containers as pods, while _services_ are responsible only for adding
+> networking features to those pods.
 
 ## Deploy and check your application