Nope; that's the actual cookie store, all right. One thing you need to be careful about when you edit or replace any preferences files in Gecko-based apps: quit the app which owns that file before you edit it.
Gecko reads in all of its preferences when it starts up, and then doesn't touch the file again until you quit. At that time, it overwrites all of the prefs files with its current settings. This has two consequences. First of all, when you edit the file with Gecko running, you won't be able to get Gecko to read in the file. Second, when you quit Gecko, it will overwrite the preferences files, which will undo any changes you've made while it was running.
Note that this phenomenon isn't unique to Gecko. Most apps work this way. However, few Mac apps have ever had human-readable preferences files, even though it's a very common thing for Unix applications. For many Unix apps, this is the only way you can change settings. Mozilla, and later the other Gecko apps, inherited the human-readable files fromthe Unix heritage of many of its developers, but then added the GUIs demanded by many Windows and Mac users: truly, the best of both worlds.