Getting started tut: updateLocations vs. UPDATE_LOCATIONS - explain the automagic!

In the getting started tutorial there is the LocationActions class and a LocationStore class. The LocationActions class defines a method (an action?) named updateLocations. However when the LocationsStore binds a handler to this action, it refers to it as LocationActions.UPDATE_LOCATIONS.

Please add a **thorough** explanation of the automagic that is going on here.

Start with the getting started tutorial and read the LocationActions and LocationsStore examples together, focusing on how updateLocations is exposed as LocationActions.UPDATE_LOCATIONS. Done means the tutorial thoroughly explains this automatic naming and binding behavior so a newcomer can understand why the two forms differ.

Written by the indexing model from the issue text.