openstack/cloudkitty-specs
Code Issues Proposed changes

Fix typos in files

Browse Source 
Change-Id: I007351039135bd7e46422ce743d694363b2aa6aa
This commit is contained in:
ShangXiao 2019-11-27 16:28:24 +08:00
parent 2879fead75
commit 5454b450e9
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/template.rst
View File

@ -113,7 +113,7 @@ Each API method which is either added or changed should have the following
inconsistent parameters supplied to the method, or when an
instance is not in an appropriate state for the request to
succeed. Errors caused by syntactic problems covered by the JSON
schema defintion do not need to be included.
schema definition do not need to be included.
* URL for the resource

2
specs/train/add_get_scope_state_api_endpoint.rst
View File

@ -10,7 +10,7 @@ Add a v2 API endpoint to retrieve the state of different scopes
https://storyboard.openstack.org/#!/story/2005395
.. note:: This spec is the detailled implementation of one part of a
.. note:: This spec is the detailed implementation of one part of a
larger spec. If you haven't read it yet, please see
https://review.opendev.org/#/c/657393/

4
specs/train/add_v2_storage_driver_elasticsearch.rst
View File

@ -185,10 +185,10 @@ Performance Impact
On most benchmarks (and from what could be determined from POCs), data insertion
into Elasticsearch is slower than insertion into InfluxDB. However,
Elasticsearch is faster for aggreations. However, once CloudKitty has caught
Elasticsearch is faster for aggregations. However, once CloudKitty has caught
up with the current timestamp, not many insertions are required. Moreover,
Elasticsearch's support for clustering and for tuning should allow for a
better overall perfomance in the end.
better overall performance in the end.
Other deployer impact
---------------------