From f5bb1c2c956651771f5de98fe6b71f1c090ca1c7 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Tue, 27 Feb 2018 23:33:42 +0800 Subject: [PATCH] Update get-swarm.md (#6067) --- swarm/get-swarm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/swarm/get-swarm.md b/swarm/get-swarm.md index 365b49c35b..60a02b684e 100644 --- a/swarm/get-swarm.md +++ b/swarm/get-swarm.md @@ -86,7 +86,7 @@ The first time you use any image, Docker Engine checks to see if you already hav Using a Swarm container has three key benefits over other methods: * You don't need to install a binary on the system to use the image. -* The single command `docker run` command gets and run the most recent version of the image every time. +* The single command `docker run` gets and runs the most recent version of the image every time. * The container isolates Swarm from your host environment. You don't need to perform or maintain shell paths and environments. Running the Swarm image is the recommended way to create and manage your Swarm cluster. All of Docker's documentation and tutorials use this method.