From d2971dfd0d24b71e154c7e7e42fc7d57b31a822b Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Fri, 11 Aug 2017 01:55:22 +0800 Subject: [PATCH] Update part3.md (#4119) * Update part3.md * Update part3.md --- get-started/part3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/get-started/part3.md b/get-started/part3.md index 7a2f02c415..8b3a5e0395 100644 --- a/get-started/part3.md +++ b/get-started/part3.md @@ -39,7 +39,7 @@ must go one level up in the hierarchy of a distributed application: the - **Services** (you are here) - Container (covered in [part 2](part2.md)) -## Understanding services +## About services In a distributed application, different pieces of the app are called "services." For example, if you imagine a video sharing site, it probably includes a service @@ -57,7 +57,7 @@ service in the process. Luckily it's very easy to define, run, and scale services with the Docker platform -- just write a `docker-compose.yml` file. -## Your first `docker-compose.yml` File +## Your first `docker-compose.yml` file A `docker-compose.yml` file is a YAML file that defines how Docker containers should behave in production.