Tweak wording of integers with ranges message

[kstich]

Background

The purpose of this validation is to push @range traits on to distinct integers in a model, so clarify the message to apply to targets.

Why not make this target members?

Having this apply to members means that each place the same potential values need to be specified, they must be kept in sync. This is prone to mistakes if the same value in the range needs to be adjusted in multiple locations.

Why not exclude the prelude smithy.api#Integer?

This doesn't solve the problem that the validation expects. Exempting members that target the prelude integer doesn't force all integer input to be bound.

Links

• See also Fix selector in RawIntegerWithoutRange examples #2966

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

This pull request does not contain a staged changelog entry. To create one, use the ./.changes/new-change command. For example:

./.changes/new-change --pull-requests "#2971" --type feature --description "Tweak wording of integers with ranges message"

Make sure that the description is appropriate for a changelog entry and that the proper feature type is used. See ./.changes/README or run ./.changes/new-change -h for more information.