Typo fix: splitted => split
Change-Id: I1c3f0b9c5196bdd961d5a32e2df2acc4f3c10301
This commit is contained in:
parent
2558a22a80
commit
45c8f44777
@ -42,7 +42,7 @@ This means that class represents single scenario which is actually implemented
|
||||
in method *Scenario.run()*.
|
||||
|
||||
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
|
||||
and another is class-based:
|
||||
|
@ -287,7 +287,7 @@ Old commands:
|
||||
uninstall Remove the deployment's local Tempest installation.
|
||||
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
|
||||
install Tempest in virtual environment via ``rally verify install`` and use
|
||||
``--system-wide`` option in ``rally verify start``.
|
||||
|
@ -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
|
||||
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
|
||||
instead of "atomic actions".
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user