add happens-before description
correct the key of a string resource
remove unnecessary modifier ' volatile'

There is no visibility problem, the happens-before rules can assure it.
As described in 'Package java.util.concurrent.atomic Description':
compareAndSet and all other read-and-update operations such as
getAndIncrement have the memory effects of both reading and writing
volatile variables.