Update docker-app-development-workflow.md (dotnet#2769)

docs/standard/microservices-architecture/docker-application-development-process/docker-app-development-workflow.md

@@ -236,7 +236,7 @@ services:
 
 Note that this docker-compose.yml file is a simplified and merged version. It contains static configuration data for each container (like the name of the custom image), which always applies, plus configuration information that might depend on the deployment environment, like the connection string. In later sections, you will learn how you can split the docker-compose.yml configuration into multiple docker-compose files and override values depending on the environment and execution type (debug or release).
 
-The docker-compose.yml file example defines five services: the webmvc service (a web application); two microservices (catalog.api and ordering.api); and two data source containers (sql.data based on SQL Server for Linux running as a container, and postgres.data as a Postgres database). Each service will be deployed as a container, so a Docker image is required for each.
+The docker-compose.yml file example defines five services: the webmvc service (a web application), two microservices (catalog.api and ordering.api), and two data source containers (sql.data based on SQL Server for Linux running as a container and postgres.data as a Postgres database). Each service is deployed as a container, so a Docker image is required for each.
 
 The docker-compose.yml file specifies not only what containers are being used, but how they are individually configured. For instance, the webmvc container definition in the .yml file: