Update opaque item wording

Author: Mark-Simulacrum

posts/2024-06-13-Rust-1.79.0.md

@@ -64,7 +64,7 @@ were not possible or imposed extra, unnecessary constraints on usage:
 * **`where` clauses** - in this position, this is equivalent to breaking up the bound into two (or more) `where` clauses. For example, `where T: Trait<Assoc: Bound>` is equivalent to `where T: Trait, <T as Trait>::Assoc: Bound`.
 * **Supertraits** - a bound specified via the new syntax is implied when the trait is used, unlike where clauses. Sample syntax: `trait CopyIterator: Iterator<Item: Copy> {}`.
 * **Associated type item bounds** - This allows constraining the *nested* rigid projections that are associated with a trait's associated types. e.g. `trait Trait { type Assoc: Trait2<Assoc2: Copy>; }`.
-* **opaque item bounds (RPIT, TAIT)** - This allows constraining associated types that are associated with the opaque without having to *name* the opaque. For example, `impl Iterator<Item: Copy>` defines an iterator whose item is `Copy` without having to actually name that item bound.
+* **opaque type bounds (RPIT, TAIT)** - This allows constraining associated types that are associated with the opaque type without having to *name* the opaque type. For example, `impl Iterator<Item: Copy>` defines an iterator whose item is `Copy` without having to actually name that item bound.
 
 See [the stabilization report](https://github.com/rust-lang/rust/pull/122055/#issue-2170532454) for more details.