From 2fc412580065bcd57217b7733fd739d1aa4a4c41 Mon Sep 17 00:00:00 2001 From: darrenchan Date: Mon, 11 May 2015 13:11:31 +1000 Subject: [PATCH] Minor edits in the HOT guide Reworded hot version configuration and added link to the HOT specification. backport: none Closes-Bug: #1431217 Change-Id: I65fc67cb658fe22f4731a8356e05517594802851 --- .../source/hot-guide/hot_hello_world.rst | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/doc/user-guide/source/hot-guide/hot_hello_world.rst b/doc/user-guide/source/hot-guide/hot_hello_world.rst index 855e3dc904..4a2f9fb16b 100644 --- a/doc/user-guide/source/hot-guide/hot_hello_world.rst +++ b/doc/user-guide/source/hot-guide/hot_hello_world.rst @@ -52,12 +52,15 @@ could be used to deploy a single compute instance: image: ubuntu-trusty-x86_64 flavor: m1.small -Each HOT template has to include the ``heat_template_version`` key with value -``2013-05-23``, the current HOT version. While the ``description`` key is -optional, it is good practice to include some useful text that describes what -users can do with the template. In case you want to provide a longer -description that does not fit on a single line, you can provide multi-line text -in YAML, for example: +Each HOT template must include the ``heat_template_version`` key with +the HOT version value, for example, ``2013-05-23``. A list of HOT template +versions can be found at `Heat Template Version +file `__ + +The ``description`` key is optional, however it is good practice to include +some useful text that describes what users can do with the template. +In case you want to provide a longer description that does not fit on +a single line, you can provide multi-line text in YAML, for example: .. code-block:: yaml