Beginner's Event Editing Written Tutorial (cutscenes, action queues, etc)

This is a nice start. I began reading it and I came across this:

Wait, didn't the text dump say $6B??
It did, it's just a little problem with the event dump. It's a little off - now you're technically right where that map loads, it's just a few lines down. Of course, I'm not gonna tell you to scroll until you see a 6B lol that'd be evil! Here's the solution, and THANK YOU Gi Nattak for telling me this trick.
Now we're on the 31 byte, with the UP ARROW key, go up two lines. A line is a row basically, like this:
http://yfrog.com/g9whatalineisp
Each different color marks a new line. Just wanting you to get that ha.
Okay, now just go up 2 lines just like I said and then do this:
Do CTRL + H (HEX search) and then freeze!
I want you to get this next step. Look back at the event dump and that sequence that we're looking for in Windhex. We're looking for the 6B byte, so in the Hex Search box, type 6B but don't click enter just yet. Here's another tip that will ENSURE that you get to the part of the event dump.
The event dump is saying to load map 17. So right after the 6B command, type 17. That should be enough bytes for you to be guaranteed that you're at the right spot in the hex editor.
Now this is what you should have in the Hex Search Box:
6B17
No spaces, no nothing, just numbers. Click Enter and VOILA, look at where Windhex jumps you to!
http://yfrog.com/htloadmapp
This is the Load Map command for that spot in the event dump! This is how EVERY event will be when you're looking for it. The reason being, is the event dump was a little off by a few offsets, nothing that major. Atleast we HAVE an event dump.
But let's recap, to find an event you should go into the event dump, search for the text nearest to it, and then copy the offset, paste it in the Hex Search Box minus the first C and omitting the '/'. Then, go up two lines and do a hex search for atleast 2 bytes. In this case - 6B and 17. Or 6B17 when you're searching for it!

While this shows an excellent set of problem-solving skills, this is actually misleading information. I personally would have never thought to do a Hex-search to find the correct offsets in such a case.

However, the reason why the EventDump offsets are different from the ROM offsets is because the EventDump was written from an unheadered ROM, while most hackers will be working from a headered ROM (since this is the version that most ROM-editing tools are written for, such as FF3usME).

The header was a section of 200 bytes at the beginning of an SNES cartridge that allowed the SNES console to read the ROM. Modern emulators do not need this header, so modern ROMs often omit it. This is why the EventDump (and most disassemblies, in fact) are written without the headered addresses.

In short, you do not need to do a Hex-search every time you want to find an offset. You simply need to add $200 bytes to whatever offset you're looking for.

However, this Hex-searching technique is a good skill to have, so you might want to mention it in your tutorial still. ...Just not in conjuction with incorrect information.