code: Clean up atomic.Value "updateable" handling

[timbray]

each of coreMatcher, fieldMatcher, and valueMatcher have an "updateable" field that is an atomic.Value used to preserve thread-safety while updates are in progress. But the naming of variables and functions isn't consistent or sensible.