Updated Argument based command permissions (markdown)

Argument-based-command-permissions.md

@@ -31,7 +31,7 @@ If the player does not have a value set for the check (in other words, it's unde
 For example, if I run `/lp user Notch clear`, LuckPerms will check for the following permissions in this order.
 
 * `luckperms.user.clear`
-* `luckperms.user.clear.modify.others` (if this check returns true, the next permission will not be checked)
+* `luckperms.user.clear.modify.others` (if this check returns true/false, the next permission will not be checked)
 * `luckperms.modify.user.others`
 
 If any of the checks return false, the action will not be allowed.
@@ -46,7 +46,7 @@ If the player does not have a value set for the check (in other words, it's unde
 For example, if I run `/lp user Luck permission info`, LuckPerms will check for the following permissions in this order.
 
 * `luckperms.user.permission.info`
-* `luckperms.user.permission.info.view.self` (if this check returns true, the next permission will not be checked)
+* `luckperms.user.permission.info.view.self` (if this check returns true/false, the next permission will not be checked)
 * `luckperms.view.user.self`
 
 If any of the checks return false, the action will not be allowed.
@@ -61,13 +61,43 @@ If the player does not have a value set for the check (in other words, it's unde
 For example, if I run `/lp user Notch permission info`, LuckPerms will check for the following permissions in this order.
 
 * `luckperms.user.permission.info`
-* `luckperms.user.permission.info.view.others` (if this check returns true, the next permission will not be checked)
+* `luckperms.user.permission.info.view.others` (if this check returns true/false, the next permission will not be checked)
 * `luckperms.view.user.others`
 
 If any of the checks return false, the action will not be allowed.
 
-### Checks when a player modifies/views another group/track
+## Checks when a player modifies/views a group
 
-### Checks when a player makes changes in a specific context
+### Modify a group
 
-### Checks when a player makes changes with a set of specific arguments
+When a player tries to use a command to modify a group, LuckPerms will first check for `[base command permission].modify.[group name]`. If this returns true, the action is will be allowed. If it returns false, the action will not be allowed.
+
+If the player does not have a value set for the check (in other words, it's undefined), LuckPerms will then check for `luckperms.modify.group.[group name]` to obtain a result. If neither checks return true, the action is not allowed.
+
+#### Example
+For example, if I run `/lp group admin clear`, LuckPerms will check for the following permissions in this order.
+
+* `luckperms.group.clear`
+* `luckperms.group.clear.modify.admin` (if this check returns true/false, the next permission will not be checked)
+* `luckperms.modify.group.admin`
+
+If any of the checks return false, the action will not be allowed.
+
+### View a group
+
+When a player tries to use a command to view data about a group, LuckPerms will first check for `[base command permission].view.[group name]`. If this returns true, the action is will be allowed. If it returns false, the action will not be allowed.
+
+If the player does not have a value set for the check (in other words, it's undefined), LuckPerms will then check for `luckperms.view.group.[group name]` to obtain a result. If neither checks return true, the action is not allowed.
+
+#### Example
+For example, if I run `/lp group admin permission info`, LuckPerms will check for the following permissions in this order.
+
+* `luckperms.group.permission.info`
+* `luckperms.group.permission.info.view.admin` (if this check returns true/false, the next permission will not be checked)
+* `luckperms.view.group.admin`
+
+If any of the checks return false, the action will not be allowed.
+
+## Checks when a player makes changes in a specific context
+
+## Checks when a player makes changes with a set of specific arguments