airship
/
deckhand
Code Issues Proposed changes

Fix typos 

This patch set fixes a handful of typographical errors in the documents.

Change-Id: Ic2b590dcf4d16ae35ed88bdc606d4bcfb2d9dd58
Signed-off-by: Tin Lam <tin@irrational.io>
This commit is contained in:
Tin Lam 2018-01-21 02:44:37 -06:00
parent feb3dd57e2
commit 1efd928206
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/api_ref.rst
View File

@ -95,7 +95,7 @@ abstract documents will be returned. This is the primary endpoint that
consumers will interact with for their configuration.
Valid query parameters are the same as for
``/revisions/{revision_id}/documents``, minus the paremters in
``/revisions/{revision_id}/documents``, minus the parameters in
``metadata.layeringDetinition``, which are not supported.
Raises a ``409 Conflict`` if a ``layeringPolicy`` document could not be found.

4
doc/source/document_types.rst
View File

@ -31,7 +31,7 @@ DataSchema
``DataSchema`` documents are used by various services to register new schemas
that Deckhand can use for validation. No ``DataSchema`` documents with names
beginning with ``deckhand/`` or ``metadata/`` are allowed. Tme ``metadata.name``
beginning with ``deckhand/`` or ``metadata/`` are allowed. The ``metadata.name``
field of each ``DataSchema`` document specifies the top level ``schema`` that it
is used to validate.
@ -89,7 +89,7 @@ allows services to check whether a particular revision (described below) of
documents meets a configurable set of validations without having to know up
front the complete list of validations.
Each validation ``name`` specified here is a reference to data that is postable
Each validation ``name`` specified here is a reference to data that is POSTable
by other services. Names beginning with ``deckhand`` are reserved for internal
use. See the Validation section below for more details.

2
doc/source/overview.rst
View File

@ -70,7 +70,7 @@ to user-provided JSON schemas.
.. note::
While Deckhand ingests YAML documents, internally it translates them to
Python objects and can use JSON schemas to valdiate those objects.
Python objects and can use JSON schemas to validate those objects.
For more information, see the :ref:`validation` section.