From f0a6ebcad29ec7eea9e08f24753499c94a642e63 Mon Sep 17 00:00:00 2001 From: chengebj5238 Date: Tue, 6 Feb 2018 17:28:39 +0800 Subject: [PATCH] Modify grammatical errors Change-Id: I68d7c34de77b664f9446dd32dada9064d83272ca --- specs/kilo/volume-sorting.rst | 4 ++-- specs/liberty/volume-migration-improvement.rst | 2 +- specs/mitaka/assisted_snapshot_improvements.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/specs/kilo/volume-sorting.rst b/specs/kilo/volume-sorting.rst index 7b8a1099..ba939ee2 100644 --- a/specs/kilo/volume-sorting.rst +++ b/specs/kilo/volume-sorting.rst @@ -147,13 +147,13 @@ returned from a detailed query is a valid sort key. Performance data was gathered by running on a simple devstack VM with 2GB memory. 5000 volumes were inserted into the DB. The data shows that the sort time on the main data table is dwarfed (see first table below) when -running a detailed query -- most of the time is spent querying the the other +running a detailed query -- most of the time is spent querying the other tables for each item; therefore, the impact of the sort key on a detailed query is minimal. For example, the data below compares the processing time of a GET request for a non-detailed query to a detailed query with various limits using the default -sort keys. The purpose of this table is to show the the processing time for a +sort keys. The purpose of this table is to show the processing time for a detailed query is dominated by getting the additional details for each item. +-------+--------------------+----------------+---------------------------+ diff --git a/specs/liberty/volume-migration-improvement.rst b/specs/liberty/volume-migration-improvement.rst index 6b327243..20fd2e49 100644 --- a/specs/liberty/volume-migration-improvement.rst +++ b/specs/liberty/volume-migration-improvement.rst @@ -189,7 +189,7 @@ REST API impact The REST API should be able to provide the migration status and the migration progress information for the volumes. For the migration status, it can be -retrieved from the database. For the the migration progress, the API request +retrieved from the database. For the migration progress, the API request will be scheduled to the cinder volume service, where the volume is located, and cinder volume service reports the updated progress back. diff --git a/specs/mitaka/assisted_snapshot_improvements.rst b/specs/mitaka/assisted_snapshot_improvements.rst index a6f217cf..dbb5653e 100644 --- a/specs/mitaka/assisted_snapshot_improvements.rst +++ b/specs/mitaka/assisted_snapshot_improvements.rst @@ -51,7 +51,7 @@ volume_admin_metadata table:: volume : relationship joining to volumes table Setting a snapshot_status metadata value will allow the API layer -to transfer this information to the the volume service. +to transfer this information to the volume service. Volume manager<->driver interaction -----------------------------------