For your first problem there's probably some compression or other weird text storage format that's causing it to mess up (or you could have just screwed up something on accident, like a pointer). Try changing only one letter; eg. Soldier -> Koldier. If that doesn't work you'll have to figure out what it's doing by looking at the assembly. Which brings us to your next question.
It sounds like there is a big gap in your understanding of how games are put together. In a ROM every byte can be labeled as either
code or
data. When most people refer to "assembly hacking" they mean editing the code. The examples you gave all would probably involve editing data, unless the game does it in a strange way (such as "hardcoding" data).
Once you figure out the location and structure of the data you wish to edit you
can easily edit it in a hex editor, though with some sorts of data (map/graphics data) it's easier to use a custom editor. There are several ways you can find the location of the data you wish to edit. ROM corruption is a method that doesn't involve knowledge of assembly, so it sometimes is easier for newbies. Debugging is the method that I personally use, you need to be familiar with the assembly code for the system you are working on (GBA uses ARM assembly). The process involves tracing the data from either it's display as graphics on the screen or from the RAM by following the assembly code of the game backwards. The techniques for this differ by system and debugger.
Now, for debugging on the GBA there are basically two utilities available.
VBA-SDL-H is a modified version of VBA. The debugging interface is sort of awkward and command line based, in my opinion it is fairly hard to use. No$GBA is my preferred debugger; it's very nice but with one huge drawback: it's not free and the author has been MIA for a while so I'm not even sure if you can still buy it. You're on your own finding a way to get a hold of a copy.
Since No$GBA might very well be impossible for you to find I'd recommend figuring out how to do ROM corruption. My favorite utitily for this is
ROM Corrupter by Dwedit. I could post a bit more in depth on how I do corruption, but I've already posted a ton of information and to be completely honest this seems a bit above your level. I recommend going through the database and reading some of the documents until you have a better understanding of how ROM hacking works in general.