Update Per-World.md

Plugins/World/Per-World.md

@@ -2,14 +2,12 @@ the basic functionality is done
 it can store and retrieve inventories, playerdata, and player locations
 
 
-THINGS I WILL ADD:
-==================
+####THINGS I WILL ADD:
+--
+"object-based" configuration:
   
+LOCATIONS:
 
-                "OBJECT-BASED" CONFIGURATION
-  
-  
-  LOCATIONS:
     world-specific, or
     categorical (ie "spawn" - every world has one)
       
@@ -21,10 +19,11 @@ THINGS I WILL ADD:
        including "none" - ie, cancel the teleport if the target world has no coords set
        for that category
        
-  EXCURSIONS:
-  an excursion is an ongoing "visit" to a world.
-  each player can have multiple stored excursions per world
-  every excursion has its own inventory and/or data
+--
+EXCURSIONS:  
+an excursion is an ongoing "visit" to a world.  
+each player can have multiple stored excursions per world  
+every excursion has its own inventory and/or data
   
     world-specific
     categorical
@@ -32,20 +31,20 @@ THINGS I WILL ADD:
       excursion tracking: some excursions might terminate if the player dies, respawning them elsewhere,
        or, perform some other action in response to an event occuring within the excursion
     
-  STORYLINES:
-  a player can have multiple storylines, each one a separate path through the server, almost like multiple
-   accounts per player. There could be, for example, a utility admin storyline, a path completely separate
-   from the admin's journey as a player
+--
+STORYLINES:  
+a player can have multiple storylines, each one a separate path through the server, almost like multiple  
+accounts per player. There could be, for example, a utility admin storyline, a path completely separate  
+from the admin's journey as a player
   
     world scope: for each storyline, set which worlds are, or are not, part of the storyline.
      those worlds when entered might default you to a different storyline, or deny your entry entirely
      until you switch to an allowed storyline for that world.
   
-  
-  
-  PLAYER TRACKING:
-  certain player data points must be tracked and stored, such as last known location, last death, number of deaths, etc.
-  These are all stored in the following way:
+--
+PLAYER TRACKING:  
+certain player data points must be tracked and stored, such as last known location, last death, number of deaths, etc.  
+These are all stored in the following way:
   
     per player
     per storyline per player