From b665acbc7157801b7ac18a051a4a3bcca0af9d7d Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Fri, 8 Jul 2016 10:55:00 -0400 Subject: [PATCH] made small changes to introduction doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit cleaned up doc added “the” where necessary and “a” where necessary to complete the sentence. changed to “The OpenStack Community” removed “a bit longer” and changed to “Longer Answer” changed to plurals where necessary Change-Id: I105829224282d3ef0ee37eb743f778283334380a --- doc/source/introduction.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/source/introduction.rst b/doc/source/introduction.rst index 969a1d0..d4db8cf 100644 --- a/doc/source/introduction.rst +++ b/doc/source/introduction.rst @@ -23,8 +23,8 @@ share the ideas of how we can evaluate, analyse and test OpenStack cloud performance, including the very infrastructure basics. As a community we want this knowledge to become publicly available to allow -OpenStack developers, QA engineers and operators to have unified way for their -projects and products evaluation and best recipes for doing this. +OpenStack developers, QA engineers and operators to have a unified way for their +projects and products evaluation and the best recipes for doing this. Who will be interested in this? ------------------------------- @@ -35,10 +35,10 @@ takes active part in either OpenStack development or its usage. Who is contributing to this guide? ---------------------------------- -Short answer: OpenStack community. +Short answer: The OpenStack community. -A bit longer answer: performance engineers from various companies, cloud -operators, OpenStack projects developers, etc. We all are part of -**Performance Team**. Therefore you can find here -test plans and methodologies, that were written keeping in mind all these -groups of people, their interest and experience. +Longer answer: performance engineers from various companies, cloud +operators, OpenStack project developers, etc. We all are part of the +**Performance Team**. Therefore, here you can find +test plans and methodologies that were written keeping in mind all of these +groups of people, their interests and experiences.