openstack/rally
Code Issues Proposed changes

Typo fix: splitted => split

Browse Source 
Change-Id: I1c3f0b9c5196bdd961d5a32e2df2acc4f3c10301
This commit is contained in:
Anh Tran 2017-02-06 13:46:57 +07:00
parent 2558a22a80
commit 45c8f44777
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/specs/implemented/class-based-scenarios.rst
View File

@ -42,7 +42,7 @@ This means that class represents single scenario which is actually implemented
in method *Scenario.run()*. in method *Scenario.run()*.
So input task can contain scenario names that does not have method part So input task can contain scenario names that does not have method part
splitted by dot from class part. split by dot from class part.
For example, here we have two scenarios, first one is in old manner For example, here we have two scenarios, first one is in old manner
and another is class-based: and another is class-based:

2
doc/specs/implemented/verification_refactoring.rst
View File

@ -287,7 +287,7 @@ Old commands:
uninstall Remove the deployment's local Tempest installation. uninstall Remove the deployment's local Tempest installation.
use Set active verification. use Set active verification.
There is another problem of old CLI. Management is splitted across all commands There is another problem of old CLI. Management is split across all commands
and you can do the same things via different commands. Moreover, you can and you can do the same things via different commands. Moreover, you can
install Tempest in virtual environment via ``rally verify install`` and use install Tempest in virtual environment via ``rally verify install`` and use
``--system-wide`` option in ``rally verify start``. ``--system-wide`` option in ``rally verify start``.

2
doc/specs/in-progress/improve_atomic_actions_format.rst
View File

@ -31,7 +31,7 @@ Also, atomic actions data does not include timestamps for each action
start and end time. Having this data will allow us to inspect atomic start and end time. Having this data will allow us to inspect atomic
actions runtime better and generate detailed reports. actions runtime better and generate detailed reports.
Since word "atomic" means something that can not be splitted into parts Since word "atomic" means something that can not be split into parts
and we introduce nested atomic actions, we should use different term and we introduce nested atomic actions, we should use different term
instead of "atomic actions". instead of "atomic actions".