Update Best Practices

Author: lbajsarowicz

docs/best-practices.md

@@ -5,12 +5,12 @@ Check out our best practices below to ensure you are getting the absolute most o
 ## Action group
 
 1. [Action group] names should be sufficiently descriptive to inform a test writer of what the action group does and when it should be used.
- Add additional explanation in comments if needed.
+ Add additional explanation in annotations if needed.
 2. Provide default values for the arguments that apply to your most common case scenarios.
 
 ## `actionGroups` vs `extends`
 
-Use an action group to wraps a set of actions to reuse them multiple times.
+Use an action group to wrap a set of actions to reuse them multiple times.
 
 Use an [extension] when a test or action group needs to be repeated with the exception of a few steps.
 
@@ -64,6 +64,12 @@ Format: {_Admin_ or _Storefront_}{Functionality}_Test.xml_, where Functionality
 
 Example: _StorefrontCreateCustomerTest.xml_.
 
+#### Action Group file name
+
+Format: {_Admin_ or _Storefront_}{Action Group Summary}ActionGroup.xml`, where Action Group Summary describes with a few words what we can expect from it.
+
+Example: _AdminCreateStoreActionGroup.xml_ 
+
 #### Section file name
 
 Format: {_Admin_ or _Storefront_}{UI Description}_Section.xml_, where UI Description briefly describes the testing UI.
@@ -97,6 +103,7 @@ Use a lower case first letter for:
 
 -  Data keys. Example: `<data key="firstName">`.
 -  Element names. Examples: `<element name="confirmDeleteButton"/>`.
+-  Step keys. For example: `<click selector="..." stepKey="clickLogin"/>`
 
 ## Page object