M #-: Spelling mistakes

Signed-off-by: dcarracedo <dcarracedo@opennebula.io>
OpenNebula · Nov 12, 2024 · 5eecc2e · 5eecc2e
1 parent 7d7c3ac
commit 5eecc2e
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/source/management_and_operations/references/template.rst b/source/management_and_operations/references/template.rst
@@ -1312,9 +1312,9 @@ In Sunstone, the ``USER_INPUTS`` can be ordered with the mouse.
 +-----------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | ``NAME``        | Yes       | Name of the user input. It has to be an existing user input name in the same template.                                                                                           |
 +-----------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| ``TITLE``       | No        | In the case of ``APP`` is the text that will be showed to the user in a Sunstone tab. In the case of ``GROUP`` is the text that will be showed to the user in a Sunstone group.  |
+| ``TITLE``       | No        | In the case of ``APP`` is the text that will be shown to the user in a Sunstone tab. In the case of ``GROUP`` is the text that will be showed to the user in a Sunstone group.   |
 +-----------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| ``DESCRIPTION`` | No        | In the case of ``APP`` is a text info note that will be showed in the APP tab. In the case of ``GROUP`` is the text that will be showed as info text in the Sunstone group.      |
+| ``DESCRIPTION`` | No        | In the case of ``APP`` is a text info note that will be shown in the APP tab. In the case of ``GROUP`` is the text that will be showed as info text in the Sunstone group.       |
 +-----------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 
 Example:

diff --git a/source/management_and_operations/vm_management/vm_templates.rst b/source/management_and_operations/vm_management/vm_templates.rst
@@ -190,9 +190,9 @@ In order to improve the user experience, Sunstone can render this user inputs in
 
 .. _sunstone_layout_rules:
 
-- User input name has to meet the following convention ``ONEAPP_<APP>_<GROUP>_<FIELD>`` where all the user inputs that meet this convention will be grouped by APP and GROUP. An APP will be render as a tab in Sunstone and a GROUP will group the user inputs that belong to this group.
-- If ``FIELD`` is the word ``ENABLED`` and the user input type is boolean, all the user inputs that has the same APP and GROUP will be hidden until the ENABLED user input is turn on.
-- If a user input not meet the convention, will be placed in a tab called Others.
+- User input name has to meet the following convention ``ONEAPP_<APP>_<GROUP>_<FIELD>`` where all the user inputs that meet this convention will be grouped by APP and GROUP. An APP will be rendered as a tab in Sunstone and a GROUP will group the user inputs that belong to this group.
+- If ``FIELD`` is the word ``ENABLED`` and the user input type is boolean, all the user inputs that have the same APP and GROUP will be hidden until the ENABLED user input is turn on.
+- If a user input not meet the convention, it will be placed in a tab called Others.
 - If all the user inputs do not meet the convention name, no tabs will be rendered (as the previous example).
 
 So, if the previous template is modified as follows: