openstack/trove-specs
Code Issues Proposed changes

Fix some spelling typo in manual

Browse Source 
taht -> that
noticable -> noticeable
utilties -> utilities

Change-Id: I4ff3e84a91503c8a0790c256dbf74132b2a9181b
Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
This commit is contained in:
Zhao Lei 2015-09-24 18:22:39 +08:00
parent 795a4946b4
commit 9c916bdce5
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/kilo/example-generator.rst
View File

@ -94,7 +94,7 @@ None.
Performance Impact
------------------
The snippet generation will run in mere seconds as part of Tox. There will be
no noticable impact on the developers of Trove.
no noticeable impact on the developers of Trove.
Other Deployer Impact
---------------------

2
specs/kilo/experimental-datastores.rst
View File

@ -34,7 +34,7 @@ It is proposed that we create three groups of datastores as described in detail
In each release, beginning with the Kilo release, each datastore will be given a classification that will be one of the values listed above based strictly on its adherence to the requirements for each of those classifications.
The classifications will be inclusive; i.e. a datastore that meets the "technical preview" requirements must also meet all the requirements for "experimental", and a datastore taht meets the "stable" requirements must also meet all the requirements for "technical preview".
The classifications will be inclusive; i.e. a datastore that meets the "technical preview" requirements must also meet all the requirements for "experimental", and a datastore that meets the "stable" requirements must also meet all the requirements for "technical preview".
Introduce a classification of strategies
----------------------------------------

2
specs/liberty/mongodb-backup-restore.rst
View File

@ -26,7 +26,7 @@ Problem Description
Backup and restore capability is important for eventually moving the MongoDB
datastore out of the "experimental" stage. MongoDB provides two utilities,
mongodump and mongorestore, which work with BSON-based files: efficient, binary
equivalents of the JSON data that MongoDB manages. These utilties will be used
equivalents of the JSON data that MongoDB manages. These utilities will be used
to provide a standard backup and restore strategy for the MongoDB datastore,
equivalent to the MySQLDump strategy for MySQL-based datastores.