From d19610946e6352ab8e59603109f5b4e718d842f7 Mon Sep 17 00:00:00 2001 From: baiwenteng Date: Fri, 9 Feb 2018 15:44:26 +0800 Subject: [PATCH] Fix wrong grammar Change-Id: I1cdf6ad68d2d5bc3c32c1dd2c696f432e65ff8f2 --- doc/source/admin/clear-containers.rst | 4 ++-- doc/source/admin/osprofiler.rst | 2 +- doc/source/user/filter-scheduler.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/admin/clear-containers.rst b/doc/source/admin/clear-containers.rst index ee0bba18b..906c229b2 100644 --- a/doc/source/admin/clear-containers.rst +++ b/doc/source/admin/clear-containers.rst @@ -4,7 +4,7 @@ Clear Containers in Zun Zun now supports running Clear Containers with regular Docker containers. Clear containers run containers as very lightweight virtual machines -which boots up really fast and has low memory footprints. It provides +which boot up really fast and has low memory footprints. It provides security to the containers with an isolated environment. You can read more about Clear Containers `here `_. @@ -33,4 +33,4 @@ To create Clear Containers with Zun, specify the `--runtime` option:: .. note:: Clear Containers support in Zun is not production ready. It is recommended - not to run Clear Containers and runc containers on the same host. + not to running Clear Containers and runc containers on the same host. diff --git a/doc/source/admin/osprofiler.rst b/doc/source/admin/osprofiler.rst index 02c2b4dca..c47506435 100644 --- a/doc/source/admin/osprofiler.rst +++ b/doc/source/admin/osprofiler.rst @@ -16,7 +16,7 @@ ====================== This is the demo for Zun integrating with osprofiler. `Zun -`_ is a OpenStack container +`_ is an OpenStack container management services, while `OSProfiler `_ provides a tiny but powerful library that is used by most OpenStack projects and diff --git a/doc/source/user/filter-scheduler.rst b/doc/source/user/filter-scheduler.rst index 8e4ef6222..2995c9a7f 100644 --- a/doc/source/user/filter-scheduler.rst +++ b/doc/source/user/filter-scheduler.rst @@ -17,7 +17,7 @@ If the Scheduler cannot find candidates for the container, it means that there are no appropriate host where that container can be scheduled. The Filter Scheduler has a set of ``filters`` that are built-in. If the -built-in filters is insufficient, you can implement your own filters with your +built-in filters are insufficient, you can implement your own filters with your filtering algorithm. There are many standard filter classes which may be used