openstack
/
fuel-specs
Code Issues Proposed changes

Fix a typo 

TrivialFix

Change-Id: Ieed3bc761d1dc320b1dfe318096c9519a6ef362e
This commit is contained in:
gengchc2 2016-12-02 15:25:58 +08:00
parent d38c8d571d
commit cf9912f539
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/9.0/converge-to-eslint-config-openstack.rst
View File

@ -206,7 +206,7 @@ Acceptance criteria
===================
The following rules need to be used from eslint-config-openstack (i.e. they
shouldn't be overriden in Fuel's .eslintrc):
shouldn't be overridden in Fuel's .eslintrc):
* complexity

2
specs/9.0/tasks-computable-fields-with-yaql.rst
View File

@ -57,7 +57,7 @@ change as this will lead to quorum loss and service degradation. As an example,
we could create an expression for task policy to be 'parallel' for new
deployment and 'one-by-one' when operating with the existing cluster.
Another benefit of this approach is that these expressions can be overriden
Another benefit of this approach is that these expressions can be overridden
with Fuel Pluggable Framework within plugins **.yaml** files bringing Fuel
onto new level of flexibility.

2
specs/9.0/upload-deployment-facts-to-configdb.rst
View File

@ -163,7 +163,7 @@ The task shall perform the following operations using ConfigDB API:
client.
The latter function ensures that the deployment process accounts for data
overriden in ConfigDB. This is required for 2nd day operations based on
overridden in ConfigDB. This is required for 2nd day operations based on
the Fuel workflow, specifically for scale-out opertaions (adding a node
to the cluster) and replacement of failed nodes.