diff --git a/FAQ.md b/FAQ.md
index 00f354e..197dc34 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -32,4 +32,25 @@ The world will become a creative world, and any players will be set to creative
 
     /mvm set mode survival
 
-Keep in mind that **ops can enter creative mode in a survival world** with the `/gamemode` command. Be careful to only op players that you trust!
\ No newline at end of file
+Keep in mind that **ops can enter creative mode in a survival world** with the `/gamemode` command. Be careful to only op players that you trust!
+
+## <a name="tp-perms"></a> Why did you change from the simple teleport permissions?
+The teleport command was becoming immensely powerful and some people don't want their users to have all this power. It is a little bit more complex, but allows for much more flexible teleportation.
+
+Now, Each [[Destination|Destinations]] type gets it's own 2 permissions (These are listed on the [[Destinations]] page). You can still give a user `multiverse.teleport.*` to give them global teleport access for themself **and** others. 
+
+If you just want them to have teleport rights to every destination type for themself: `multiverse.teleport.self.*`   
+_**HINT:** This is the same as the old `multiverse.core.tp.self` permission!_
+
+This also allows for very advanced setups like "I want people to be able to teleport **only themselves** everywhere **except** other players! Cuz that's cheating!":
+
+With PermissionsBukkit (just an example, you should be able to do the same with your perms plugin)
+
+    > perm group setperm moderator multiverse.teleport.other.* false
+    09:56:46 [INFO] Group moderator now has multiverse.teleport.other.* = false.
+    
+    > perm group setperm moderator multiverse.teleport.self.* true
+    09:56:47 [INFO] Group moderator now has multiverse.teleport.self.* = true.
+    
+    > perm group setperm moderator multiverse.teleport.self.pl false
+    09:56:48 [INFO] Group moderator now has multiverse.teleport.self.pl = false.