[royale-docs] branch master updated: Update jewel-hgroup.md

[an...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

andreww pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new 9bb29f2  Update jewel-hgroup.md
9bb29f2 is described below

commit 9bb29f2772128c0bfe1c6f6ea0555f53bd8ae1b1
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Fri Oct 2 17:41:25 2020 -0300

    Update jewel-hgroup.md
    
    Minor text edits
---
 component-sets/jewel/jewel-hgroup.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/component-sets/jewel/jewel-hgroup.md b/component-sets/jewel/jewel-hgroup.md
index 2f4f7b2..65107ca 100644
--- a/component-sets/jewel/jewel-hgroup.md
+++ b/component-sets/jewel/jewel-hgroup.md
@@ -35,7 +35,7 @@ Available since version __0.9.7__.
 
 ## Overview
 
-The Jewel HGroup class is a [Group](component-sets/jewel/group) that layout elements horizontaly and provide some properties to allow more flexibility like `gap` to define some spacing between items, or `itemsHorizontalAlign` and `itemsVerticalAlign`, to distribute elements in different ways along horizontal and vertical axis respectively.
+The Jewel HGroup class is a [Group](component-sets/jewel/group) that lays out elements horizontally and provides some properties to allow more flexibility like `gap` to define spacing between items, and `itemsHorizontalAlign` and `itemsVerticalAlign` to distribute elements in different ways along the horizontal or vertical axis.
 
 ## Example of use
 
@@ -64,7 +64,7 @@ hg.addElement(label);
 parent.addElement(hg);
 ```
 
-where `parent` is the container where the HGroup will be added.
+where `parent` is the container to which the HGroup will be added.
 
 ## Relevant Properties and Methods
 
@@ -96,9 +96,9 @@ where `parent` is the container where the HGroup will be added.
 
 ## Relevant Events
 
-The most important event is `initComplete`, which indicates that the initialization of the group is complete.
+The most important event is `initComplete`, which indicates that initialization of the group is complete.
 
-Is needed when some action coded in a callback function need to be triggered as the group is ready to use after initialization.
+It is needed when some action coded in a callback function needs to be triggered when the group is ready to use after initialization.
 
 You can attach callback listeners to the _initComplete_ event in __MXML__ as follows:
 
@@ -106,7 +106,7 @@ You can attach callback listeners to the _initComplete_ event in __MXML__ as fol
 <j:HGroup initComplete="initCompleteHandler(event)"/>
 ```
 
-the _initComplete_ event will use the `initCompleteHandler` callback function you provide in __ActionScript__:
+the _initComplete_ event uses the `initCompleteHandler` callback function you provide in __ActionScript__:
 
 ```mxml
 <fx:Script>