grammar corrections

Change-Id: I30a5ae55e117605c414ffd0fd3d3e80222a2c5a3
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann
2018-01-05 10:42:48 -05:00
parent 96b4e448d3
commit fbfa20a8c6
4 changed files with 4 additions and 4 deletions

View File

@@ -11,7 +11,7 @@ assert:supports-accessible-upgrade
==================================
This tag is part of the assert category of tags, which are assertions made by
the project team themselves about their deliverables maturity.
the project team themselves about the maturity of their deliverables.
The ``assert:supports-accessible-upgrade`` tag asserts that in addition to a
deliverable supporting basic :ref:`upgrade capabilities

View File

@@ -11,7 +11,7 @@ assert:supports-rolling-upgrade
===============================
This tag is part of the assert category of tags, which are assertions
made by the project team themselves about their deliverables maturity. One
made by the project team themselves about the maturity of their deliverables. One
such assertion (or self-imposed contract) is about the rolling upgrade
features that the deliverable supports.

View File

@@ -11,7 +11,7 @@ assert:supports-upgrade
=======================
This tag is part of the assert category of tags, which are assertions
made by the project team themselves about their deliverables maturity. One
made by the project team themselves about the maturity of their deliverables. One
such assertion (or self-imposed contract) is about the cold-upgrade
features that the deliverable supports.

View File

@@ -11,7 +11,7 @@ assert:supports-zero-downtime-upgrade
=====================================
This tag is part of the assert category of tags, which are assertions made by
the project team themselves about their deliverables maturity.
the project team themselves about the maturity of their deliverables.
The ``assert:supports-zero-downtime-upgrade`` tag asserts that in addition to a
deliverable supporting `minimal rolling upgrade capabilities