openstack/glance
Code Issues Proposed changes

Fix use of etc. in metadefs docs.

Browse Source 
OpenStack house style is no Latin, which includes "etc.".
This fixes the usage in the metadefs documentation.

Change-Id: Ic88bd2a9286b2647a927f2fb8ecdec480053a91c
Closes-Bug: 1610311
This commit is contained in:
Travis Tripp 2016-08-05 16:42:20 -06:00
parent b9ec22ca01
commit 5829139ccf
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
api-ref/source/v2/metadefs-index.rst
View File

@ -31,7 +31,9 @@ General information
The Metadata Definitions Service ("metadefs", for short) provides a common API The Metadata Definitions Service ("metadefs", for short) provides a common API
for vendors, operators, administrators, services, and users to meaningfully for vendors, operators, administrators, services, and users to meaningfully
define available key:value pairs that can be used on different types of cloud define available key:value pairs that can be used on different types of cloud
resources (for example, images, artifacts, volumes, flavors, aggregates, etc). resources (for example, images, artifacts, volumes, flavors, aggregates,
and other resources).
To get you started, Glance contains a default catalog of metadefs that may be To get you started, Glance contains a default catalog of metadefs that may be
installed at your site; see the `README installed at your site; see the `README
<https://github.com/openstack/glance/tree/master/etc/metadefs/README>`_ in the <https://github.com/openstack/glance/tree/master/etc/metadefs/README>`_ in the

6
doc/source/metadefs-concepts.rst
View File

@ -23,9 +23,9 @@ OpenStack.
It provides a common API for vendors, admins, services, and users to It provides a common API for vendors, admins, services, and users to
meaningfully **define** available key / value pair metadata that meaningfully **define** available key / value pair metadata that
can be used on different types of resources (images, artifacts, volumes, can be used on different types of resources (images, artifacts, volumes,
flavors, aggregates, etc). A definition includes a property's key, flavors, aggregates, and other resources). A definition includes a property's
its description, its constraints, and the resource types to which it can be key, its description, its constraints, and the resource types to which it
associated. can be associated.
This catalog does not store the values for specific instance properties. This catalog does not store the values for specific instance properties.