From 1c673b92e6b54a9f9a08735824aa460f942d765c Mon Sep 17 00:00:00 2001 From: blue55 Date: Fri, 25 Aug 2017 09:40:59 +0800 Subject: [PATCH] modify some misspellings Change-Id: I975d5ac17ea8f34f5fc70b16bdb648b95fb9a4f7 --- doc/specs/implemented/db_refactoring.rst | 2 +- doc/specs/implemented/improve_scenario_output_format.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/specs/implemented/db_refactoring.rst b/doc/specs/implemented/db_refactoring.rst index 943a42b9..321fcc81 100644 --- a/doc/specs/implemented/db_refactoring.rst +++ b/doc/specs/implemented/db_refactoring.rst @@ -106,7 +106,7 @@ New DB schema * Workload - aggregated information about some specific workload (required for reports) as well as information how these workloads are executed in parallel/serial and status of each workload. Without workloads table we - won't be able to support multiple workloads per single subtas + won't be able to support multiple workloads per single subtask * WorkloadData - contains chunks of raw data for future data analyze and reporting. This is complete information that we don't need always, as well diff --git a/doc/specs/implemented/improve_scenario_output_format.rst b/doc/specs/implemented/improve_scenario_output_format.rst index 751f7b7a..37c2d5b3 100644 --- a/doc/specs/implemented/improve_scenario_output_format.rst +++ b/doc/specs/implemented/improve_scenario_output_format.rst @@ -126,7 +126,7 @@ Here is proposed iterations results structure for output data: # because this data does not require processing - it is # already processed and represents a result of Chart.render() {"title": "Interesting data from specific iteration", - "description": "Some details explaind here", + "description": "Some details explained here", "widget": "StackedArea", "data": [ [