[mesos] branch master updated: Update nested-container-and-task-group.md

[vi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

vinodkone pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git


The following commit(s) were added to refs/heads/master by this push:
     new fc41758  Update nested-container-and-task-group.md
fc41758 is described below

commit fc41758f15bb0d2b7c4294e36f6aa5e5d248f147
Author: Tarun Gupta Akirala <ta...@users.noreply.github.com>
AuthorDate: Wed Jun 20 18:49:00 2018 -0700

    Update nested-container-and-task-group.md
---
 docs/nested-container-and-task-group.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/nested-container-and-task-group.md b/docs/nested-container-and-task-group.md
index 0026366..3325ff8 100644
--- a/docs/nested-container-and-task-group.md
+++ b/docs/nested-container-and-task-group.md
@@ -14,11 +14,11 @@ some resources (e.g., network namespace, volumes) but not others
 (e.g., container image, resource limits). Here are the use cases for
 pod:
 
-* Run a side-car container (e.g., logger, backup) next the main
+* Run a side-car container (e.g., logger, backup) next to the main
   application controller.
 * Run an adapter container (e.g., metrics endpoint, queue consumer)
   next to the main container.
-* Run transient tasks inside a pod for a operations which are
+* Run transient tasks inside a pod for operations which are
   short-lived and whose exit does not imply that a pod should
   exit (e.g., a task which backs up data in a persistent volume).
 * Provide performance isolation between latency-critical application