From e572a834f2d4c058f796a1e006b3f96a960e76fe Mon Sep 17 00:00:00 2001 From: Guo Ruijing Date: Thu, 7 Jul 2016 16:36:11 +0800 Subject: [PATCH] Fix Typo in create plugin Change-Id: Id8afeec53fa9861e664a416b319234899fde326e Signed-off-by: Guo Ruijing --- .../create-plugin/create-auto-plugin.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/plugindocs/fuel-plugin-sdk-guide/create-plugin/create-auto-plugin.rst b/plugindocs/fuel-plugin-sdk-guide/create-plugin/create-auto-plugin.rst index beec5f515..bfadcd975 100644 --- a/plugindocs/fuel-plugin-sdk-guide/create-plugin/create-auto-plugin.rst +++ b/plugindocs/fuel-plugin-sdk-guide/create-plugin/create-auto-plugin.rst @@ -60,8 +60,8 @@ The automatically generated plugin does the following: |``tasks.yaml`` |Deprecated, use ``deployment_tasks.yaml`` instead | +----------------------------------------------+--------------------------------------------------+ |``volumes.yaml`` |Mapping between node roles and volume allocation. | - | |You can also define new volumesand map them to the| - | |new or existing nodes. | + | |You can also define new volumes and map them to | + | |the new or existing nodes. | +----------------------------------------------+--------------------------------------------------+ #. Build the automatically generated plugin: @@ -113,4 +113,4 @@ You can also verify the plugin installation using Fuel CLI: Enabling a plugin after deployment makes sense only in one case: when this adds a new node role and a node with this role can be added after the environment is deployed. In this case use the keyword - ``is_hotppluggable`` in ``metadata.yaml`` \ No newline at end of file + ``is_hotppluggable`` in ``metadata.yaml``