From da87b5d87a90e34c3795f949807c0ba3e9cdd5cc Mon Sep 17 00:00:00 2001 From: venkatamahesh Date: Sat, 22 Aug 2015 06:00:07 +0530 Subject: [PATCH] Word spells have been corrected Change-Id: I7deb1deaad7d45cd740fb7b0978e7722af8dd704 Closes-Bug: #1487572 --- doc/feature_request/multi_scenarios_load_gen.rst | 2 +- doc/feature_request/persistence_benchmark_env.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/feature_request/multi_scenarios_load_gen.rst b/doc/feature_request/multi_scenarios_load_gen.rst index 36373695..960f2510 100644 --- a/doc/feature_request/multi_scenarios_load_gen.rst +++ b/doc/feature_request/multi_scenarios_load_gen.rst @@ -26,7 +26,7 @@ Possible solution ----------------- * Extend Rally task benchmark configuration in such way to support passing - multiple benchmark scenarios in singe benchmark context + multiple benchmark scenarios in single benchmark context * Extend Rally task output format to support results of multiple scenarios in single benchmark separately. diff --git a/doc/feature_request/persistence_benchmark_env.rst b/doc/feature_request/persistence_benchmark_env.rst index cf0b1d0c..87797d4b 100644 --- a/doc/feature_request/persistence_benchmark_env.rst +++ b/doc/feature_request/persistence_benchmark_env.rst @@ -7,7 +7,7 @@ Use Case To benchmark many of operations like show, list, detailed you need to have already these resource in cloud. So it will be nice to be able to create -benchmark environment once before benchmarking. The run some amount of +benchmark environment once before benchmarking. So run some amount of benchmarks that are using it and at the end just delete all created resources by benchmark environment.