From c2b6563a021683aadfef6268cdacb958f4b9f818 Mon Sep 17 00:00:00 2001 From: gaobin Date: Thu, 15 Nov 2018 11:32:31 +0800 Subject: [PATCH] Some mixing errors Change-Id: I4d6f9bea6007a982c4cf7c5b4821b6b00af790e8 --- doc/source/contributor/new_developers.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/contributor/new_developers.rst b/doc/source/contributor/new_developers.rst index 1cbdcb08..eabb4470 100644 --- a/doc/source/contributor/new_developers.rst +++ b/doc/source/contributor/new_developers.rst @@ -47,7 +47,7 @@ Repositories that are part of TripleO shared with the UI. * tripleo-docs: - Where these docs are kept. :) + Where these docs are kept. * tripleo-image-elements: Image elements (snippets of puppet that prepare specific parts of the @@ -94,7 +94,7 @@ interface functions along side the command line interface. - Ensure that any new feature is provided through Rest API in form of Mistral actions, workflow or by directly accessing an OpenStack service API. -- Ensure that GUI and CLI can both operate this feature through this API +- Ensure that GUI and CLI can both operate this feature through this API. - Start your feature work by creating Mistral action or Mistral workflow - defining inputs and outputs. This is necessary so that the CI and UI have feature parity and both use the same API calls to implement a given feature. @@ -104,7 +104,7 @@ interface functions along side the command line interface. for more information. - Ensure there are unit tests where possible. - Maintain backwards compatibility with our existing template interfaces from - tripleo-heat-templates + tripleo-heat-templates. - New features should be reviewed by cores who have knowledge in that area of the codebase. - One should consider logging and support implications. If you have new logs,