essinit.md

@@ -167,7 +167,9 @@ Prompts a GUI where the user can see the old event names listed in a text editor
 If you would like to use the config to help rename your events you need to place the name of a event renaming file that matches the a specific design.
 Use  something like ```[erename],'Eyes_Erename.txt'``` in the config, and make sure your file is on the matlab path. :so: Store it in the *analysis/support/misc* folder so its on the path and you can use it later for reference.  
 
-The event renaming reference file should look like this:
+The event renaming reference file should look like this:  
+:warning:  Note there are only 3 columns! The first number in each row is my text editor displaying the line number!   
+
 ![erenamefile1](/uploads/281357a5d0cef623f1168f7d37bce061/erenamefile1.png)
 ...
 
@@ -175,7 +177,10 @@ The event renaming reference file should look like this:
 
 Where the first column is the file number, in reference to your merges, the second column is the existing event code, and the third column is the new event name. In the example above we were interested in the file one events only so they are renamed to understandable names. The events codes for the second file are left as is. You can add extra events that do not exist by accident, but make sure you do not leave one of your event codes out, as the name will be  set to empty. Separate the columns by spaces.
 
-:warning:  Note there are only 3 columns above! The first number in each row is my text editor displaying the line number! 
+The next example has a range of codes for each image for example *house_up* is codes 11-16. This file will combine these so they all have the same name.
+![erenamefile3](/uploads/59a7191bfba6e931eb9a45398b5f82f3/erenamefile3.png)  
+
+
 
 ***