Fix typos in spec template
This patch fixes few typos in the template file. Change-Id: Ic7001437645355fedc3903c83cd1a1efa3f58d16
This commit is contained in:
parent
e2d143ede4
commit
857d85710a
@ -97,7 +97,7 @@ Questions which need to be addressed by this section include:
|
||||
* What database migrations will accompany this change.
|
||||
|
||||
* How will the initial set of new data objects be generated, for example if you
|
||||
need to take into account existing instances, or modify other existing data
|
||||
need to take into account existing volumes, or modify other existing data
|
||||
describe how that will work.
|
||||
|
||||
REST API impact
|
||||
@ -118,10 +118,10 @@ Each API method which is either added or changed should have the following
|
||||
|
||||
* A description for each possible error code should be included
|
||||
describing semantic errors which can cause it such as
|
||||
inconsistent parameters supplied to the method, or when an
|
||||
instance is not in an appropriate state for the request to
|
||||
inconsistent parameters supplied to the method, or when a
|
||||
volume 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
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user