openstack/heat-specs
Code Issues Proposed changes

Wrong usage of "a/an"

Browse Source 
Wrong usage of "a/an" in the messages:
"support passing an new option specifying"
"create an multinode test setup"
"attributes also becomes a issue"

Should be:
"support passing a new option specifying"
"create a multinode test setup"
"attributes also becomes an issue"

Totally 3 occurrences in heat-specs liberty base code.

Change-Id: I1384f92e7e198afb5367a2f3d2f23b1da2b5812f
This commit is contained in:
hgangwx
2015-12-30 15:16:01 +08:00
parent 6c40a53dd2
commit 4b7e36c7f7
5 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
specs/juno/events-pagination.rst
View File

@@ -28,7 +28,7 @@ retrieve a subset of events.
Problem description
===================
It is now highly probable that a event-list call could
It is now highly probable that an event-list call could
end up attempting to return hundreds of events(especially for
AutoScalingGroup resources). At a certain point Heat
starts responding with a 500 error because the response is too large.

2
specs/kilo/ceilometer-gnocchi-alarm.rst
View File

@@ -83,7 +83,7 @@ None
Usage Scenario
==============
I want to create a autoscaling group that scale down when a statistics against
I want to create an autoscaling group that scale down when a statistics against
cpu_util of a group of vm computed by Gnocchi, reach a certain threshold::
resources:

2
specs/liberty/multi-region-test.rst
View File

@@ -35,7 +35,7 @@ and openstack-infra/project-config to allow this test to run as a gate test.
Alternatives
------------
In case it turns out to be impossible to create an multinode test setup with
In case it turns out to be impossible to create a multinode test setup with
multiple regions in the openstack infrastructure, this scenario test could also
be added as a local-only test which is not ran at the gate.

2
specs/liberty/support-to-generate-hot-templates.rst
View File

@@ -55,7 +55,7 @@ Target Milestone for completion:
Work Items
----------
* Update the heat API to support passing an new option specifying
* Update the heat API to support passing a new option specifying
the required template type. Return the cfn template if not specify
the new option.
* Update python-heatclient to expose this new option.

2
specs/liberty/type-in-attributes-schema.rst
View File

@@ -19,7 +19,7 @@ Problem description
Currently there is no way to find out what is the type of attribute returned
by the get_attr function. This makes it difficult for the template authors to
figure out what type of value will be returned. Indexing and Mapping on the
attributes also becomes a issue without the knowledge of the attribute type.
attributes also becomes an issue without the knowledge of the attribute type.
Proposed change
===============