openstack
/
governance
Code Issues Proposed changes

fix a few rst issues 

Correct a few markup errors that introduced warnings into the build.

Change-Id: Ie7f5b7eac01a5be7298ab9c5517e5c1fc4f0edbb
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2016-03-30 07:38:03 -04:00
parent 2dd0a72db7
commit a597e88322
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
resolutions/20151211-bring-your-own-kernel.rst
View File

@ -8,7 +8,7 @@ clear in the intent to provide a unified user experience across many OpenStack
clouds.
It is the opinion of the OpenStack Technical Committee that the following statements
should be true in the definition of an _`OpenStack Powered Compute`_ cloud.
should be true in the definition of an `OpenStack Powered Compute`_ cloud.
The following use key words as found in `RFC 2119`_.
@ -35,7 +35,7 @@ provides to a running server instance. In order to test the interfaces that a
user of an OpenStack cloud should be able to expect (for instance, does
config-drive show up, does the instance have the IP that neutron says it has)
we have to be able to have tests in the gate. Since OpenStack follows
`The Four Opens`_
:doc:`The Four Opens <../reference/new-projects-requirements>`
that means that our tests must be Open Source. Alternate versions of the tests
that might test the same interfaces but use Close Source Operating Systems are
not possible to be validated since we can't run those Operating Systems in the
@ -62,3 +62,4 @@ divergent from what OpenStack clouds are.
.. _RFC 2119: https://www.ietf.org/rfc/rfc2119.txt
.. _OpenStack Powered Compute: http://www.openstack.org/brand/interop/
.. _The Four Opens:

2
resolutions/index.rst
View File

@ -9,7 +9,7 @@ be expressed as a resolution.
====
.. toctree::
:maxdepth: 1
:maxdepth: 1
:glob:
2016*