Avoid abbreviations for strings and enums

[marcoscaceres]

This pull request makes a minor update to the documentation for using strings as constant values. The change clarifies that abbreviations should be avoided, as they can make code harder to read.

Closes #599

---

Preview | Diff

[Copilot]

Pull Request Overview

This PR updates documentation to provide clearer guidance on string and enum naming conventions. The change adds explicit advice to avoid abbreviations when using strings as constants or enumerated values, emphasizing code readability.

• Added guidance to avoid abbreviations in string constants and enums

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[jyasskin]

This is an example of "Value readability over brevity" in the next non-example paragraph. How about

Value readability over brevity.
Often this means to avoid abbreviations.
Keep in mind, however, that

You could add the "UI" example into that example. It might be good to also have an example of when the abbreviation was a mistake.

[marcoscaceres]

I think Intl namespace was a mistake from ECMA was a mistake. Would other folks here agree?

[jyasskin]

This would fit better into the "Value readability over brevity." paragraph and the example that follows it, but this is good enough for me.

[martinthomson]

I agree with Jeffrey. This is more naturally under "brevity".