Fix grammatical and formatting errors in documentation

Change-Id: If2b2adc8854439450347da7803f35d5de0c7c380

doc/source/plugins.rst

@@ -32,7 +32,7 @@ Plugins can be quickly written and used, with no need to contribute them to the
 Example: Benchmark scenario as a plugin
 ---------------------------------------
 
-Let's create as a plugin a simple scenario which lists flavors.
+Let's create as a plugin a simple scenario which list flavors.
 
 Creation
 ^^^^^^^^
@@ -52,7 +52,7 @@ Inherit a class for your plugin from the base *Scenario* class and implement a s
             """Sample of usage clients - list flavors
 
             You can use self.context, self.admin_clients and self.clients which are
-            initialized on scenario instanse creation"""
+            initialized on scenario instance creation"""
             self.clients("nova").flavors.list()
 
         @base.atomic_action_timer("list_flavors_as_admin")

doc/user_stories/keystone/authenticate.rst

@@ -4,23 +4,20 @@
 
 *(Contributed by Neependra Khare, Red Hat)*
 
-Below we describe how we were able to get and verify a 4x better performance of Keysone inside Apache. To do that, we ran a Keystone token creation benchmark with Rally under different load (this benchmark scenario essentially just authenticates users with keystone to get tokens).
+Below we describe how we were able to get and verify a 4x better performance of Keysone inside Apache. To do that, we ran a Keystone token creation benchmark with Rally under different load (this benchmark scenario essentially just authenticate users with keystone to get tokens).
 
 Goal
 ----
 - Get the data about performance of token creation under different load.
-- Ensure that keystone with increased public_workers/admin_workers values
+- Ensure that keystone with increased public_workers/admin_workers values and under Apache works better than the default setup.
-  and under Apache works better than the default setup.
 
 Summary
 -------
 - As the concurrency increases, time to authenticate the user gets up.
-- Keystone is CPU bound process and by default only one thread of keystone-all process get
+- Keystone is CPU bound process and by default only one thread of keystone-all process get started. We can increase the parallelism by:
-  started. We can increase the parallelism by :-
+    1. increasing public_workers/admin_workers values in keystone.conf file
-  1. increasing public_workers/admin_workers values in keystone.conf file
+    2. running keystone inside Apache
-  2. running keystone inside Apache
+- We configured Keystone with 4 public_workers and ran Keystone inside Apache. In both cases we got upto 4x better performance as compared to default keystone configuration.
-- We configured Keystone with 4 public_workers and ran Keystone inside Apache. In both
-  cases we got upto 4x better performance as compared to default keystone configuration.
 
 Setup
 -----

samples/plugins/scenario/scenario_plugin.py

@@ -24,7 +24,7 @@ class ScenarioPlugin(base.Scenario):
         """Sample of usage clients - list flavors
 
         You can use self.context, self.admin_clients and self.clients which are
-        initialized on scenario instanse creation.
+        initialized on scenario instance creation.
         """
         self.clients("nova").flavors.list()