Updated Rules (markdown)

Rules.md

@@ -31,11 +31,11 @@ Every rule needs to follow this syntax:
 Alternatively you can end the rule with `break`.<br>
 **`break`** will stop the execution for all the triggers that follow this rule inside the rule set. If a trigger that ends with `break` occurs, the following triggers of that rule set will not be executed. This allows the rules to somewhat simulate an "IF THEN" statement. 
 
-Rules are defined by using the [`Rule<x>`](Commands#rule) command. After defining one you have to activate the rule (turn it on) using `Rule<x> 1`. Similarly you can deactivate the rule using `Rule<x> 0`. 
+Rule sets are defined by using the [`Rule<x>`](Commands#rule) command. After defining one you have to activate the rule set (turn it on) using `Rule<x> 1`. Similarly you can deactivate the rule set using `Rule<x> 0`. 
 
-See [Commands](Commands#Rules) for a complete list of rules related commands.
+> See [Commands](Commands#Rules) for a complete list of rules related commands.
 
-There are 3 separate rule sets called `Rule1`, `Rule2` and `Rule3`. Each rule set can contain as many rules as can fit within the 512 character limit. Whenever a rule set is active all the rules in it will fire.
+There are 3 separate rule sets called `Rule1`, `Rule2` and `Rule3`. Each rule set can contain as many rules as can fit within the 512 character limit. Whenever a rule set is active all the rules in it will execute.
 
 Rules inside a rule set can be concatenated and have to be in one line:
 
@@ -43,7 +43,7 @@ Rules inside a rule set can be concatenated and have to be in one line:
 
 Spaces after `on`, around `do` and before `endon` or `break` are mandatory. A rule is **not** case sensitive.
 
-Example of a complete define rule command:
+Example of a define rule set command:
 ```
 Rule1 on <trigger1> do <command> break on <trigger2> do <command> endon
 ```