Updated Permissions (markdown)

Permissions.md

@@ -34,7 +34,7 @@ Setting up the permissions in the config is pretty straight forward. You may fin
 With this setup, all users will have the ability to teleport themselves using the [`/mvtp`](https://github.com/Herocraft/Multiverse-Core/wiki/Command-Reference#teleport) command, while users assigned to the admin group will also have the ability create worlds. Notice also that the admin has `permissions.*: true` and therefore can use the PermissionsBukkit commands in game. This may be especially useful for Multiverse 2.
 
 ### MV2 Permissions
-Unfortunately you can not currently set a permission node wildcard with multiverse like: `multiverse.*` in the config, so you must list out every individual permission that you need a group to have. This will change as soon as Bukkit allows permissions mutability, but in the meantime, while this may seem like a pain, there are luckily some simpler ways to handle this situation.
+You can use: `multiverse.*` to give someone all permissions for Multiverse. If you only want to give someone access to all worlds, use: `multiverse.access.*` for example.
 
 ## Setting Permissions in game
 Multiverse has the courtesy to show which permission node is needed for a command if you enter a /command and it fails due to permissions. Having this info readily available to you in the game can save you some time looking up the permission, and allow you to enter that permission into a group on the spot if need be. An admin can simply enter permissions in as you need them. For example you try to run [`/mvlist`](https://github.com/Herocraft/Multiverse-Core/wiki/Command-Reference#list) and oh my you dont have permission, but you will be notified that you need `multiverse.world.list` permission node. Entering