Fix misuse of *usage* in rule identifiers

In the prior commit, we fixed prose occurrences of *usage*.  The same
reasoning applies to the rule identifiers.

These rules describe where the language permits a construct to appear.
On the surface, that may seem to be a kind of pattern of use, but it's
not (in the sense implied by *usage*), and ultimately *use* is still
the right word.  The word *usage* describes conventions and customs --
i.e., *customary* patterns of use.  It describes how a community uses
something and how that varies, e.g., across regions.

That's not what we're doing here.  We're not describing better or
worse Rust idioms.  There's no "nonstandard usage" of Rust grammatical
constructs -- that's not what we're defining, at least.

Let's fix each rule identifier to use `use` instead.

(None of these identifiers were referenced elsewhere in
the Reference.)
6 files changed
tree: cd2e8da81bd0a11ba38a36d22c0fab56924ce677
  1. .cargo/
  2. .github/
  3. dev-guide/
  4. docs/
  5. src/
  6. theme/
  7. tools/
  8. .gitattributes
  9. .gitignore
  10. book.toml
  11. Cargo.lock
  12. Cargo.toml
  13. CONTRIBUTING.md
  14. LICENSE-APACHE
  15. LICENSE-MIT
  16. README.md
  17. reference.md
  18. rust-toolchain.toml
  19. rustfmt.toml
  20. triagebot.toml
README.md

The Rust Language Reference

This document is the primary reference for the Rust programming language.

Contributor docs

See the Reference Developer Guide for information on contributing to the Reference.