More assertive tone for specs

Putting 'should be' in spec descriptions is redundant, since all specs
describe what the code 'should' do. It is more concise to simply
state what the code *does*.