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.
| ... | ... |
@@ -79,7 +79,7 @@ Docker uses a client-server architecture. The Docker *client* talks to the |
| 79 | 79 |
Docker *daemon*, which does the heavy lifting of building, running, and |
| 80 | 80 |
distributing your Docker containers. Both the Docker client and the daemon *can* |
| 81 | 81 |
run on the same system, or you can connect a Docker client to a remote Docker |
| 82 |
-daemon. The Docker client and service communicate via sockets or through a |
|
| 82 |
+daemon. The Docker client and daemon communicate via sockets or through a |
|
| 83 | 83 |
RESTful API. |
| 84 | 84 |
|
| 85 | 85 |
 |