From 8b07fc75ffe53d8e8226c35af549f5955f4f33ad Mon Sep 17 00:00:00 2001 From: lixiaobing10051267 Date: Mon, 8 Aug 2016 14:47:15 +0800 Subject: [PATCH] Fix typo for docker swarm description Signed-off-by: lixiaobing10051267 Upstream-commit: eb4b965ddbe0c351df45dfd81b32c08c7194d804 Component: engine --- components/engine/docs/swarm/how-swarm-mode-works/services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/engine/docs/swarm/how-swarm-mode-works/services.md b/components/engine/docs/swarm/how-swarm-mode-works/services.md index 3e709b81a3..0ae9807fd3 100644 --- a/components/engine/docs/swarm/how-swarm-mode-works/services.md +++ b/components/engine/docs/swarm/how-swarm-mode-works/services.md @@ -68,7 +68,7 @@ The underlying logic of Docker swarm mode is a general purpose scheduler and orchestrator. The service and task abstractions themselves are unaware of the containers they implement. Hypothetically, you could implement other types of tasks such as virtual machine tasks or non-containerized process tasks. The -scheduler and orchestrator are agnostic about they type of task. However, the +scheduler and orchestrator are agnostic about their type of task. However, the current version of Docker only supports container tasks. The diagram below shows how swarm mode accepts service create requests and