From 14ffde2d8c67065a24930e0ac0844099cbc2cfa8 Mon Sep 17 00:00:00 2001 From: SeongJae Park Date: Tue, 8 Jul 2014 14:50:57 +0900 Subject: [PATCH] understanding-docker: Use consistent term Term 'service' was used together with 'daemon'. It would be better to use the term 'daemon' solely because most part of documentation are using the term. --- docs/sources/introduction/understanding-docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/introduction/understanding-docker.md b/docs/sources/introduction/understanding-docker.md index 18b8d5926a..8cdab02c4c 100644 --- a/docs/sources/introduction/understanding-docker.md +++ b/docs/sources/introduction/understanding-docker.md @@ -79,7 +79,7 @@ Docker uses a client-server architecture. The Docker *client* talks to the Docker *daemon*, which does the heavy lifting of building, running, and distributing your Docker containers. Both the Docker client and the daemon *can* run on the same system, or you can connect a Docker client to a remote Docker -daemon. The Docker client and service communicate via sockets or through a +daemon. The Docker client and daemon communicate via sockets or through a RESTful API. ![Docker Architecture Diagram](/article-img/architecture.svg)