w

Author: lcnr

src/solve/candidate-preference.md

@@ -167,7 +167,7 @@ where
 
 #### Why no preference for global where-bounds
 
-Global where-bounds are either fully implied by an impl or unsatisfiable. If they are unsatisfiable, we don't really care what happens. If a where-bound is fully implied then using the impl to prove the trait goal cannot result in additional constraints. This is only useful for where-bounds which use `'static`:
+Global where-bounds are either fully implied by an impl or unsatisfiable. If they are unsatisfiable, we don't really care what happens. If a where-bound is fully implied then using the impl to prove the trait goal cannot result in additional constraints. For trait goals this is only useful for where-bounds which use `'static`:
 
 ```rust
 trait A {
@@ -181,9 +181,7 @@ where
     x.test();
 }
 ```
-More importantly, by using impls to prove goals also proven by a global where-bound, we do not consider impls to be shadowed when normalizing associated types.
-
-There are no known issues from preferring impls over global where-bounds.
+More importantly, by using impls here we prevent global where-bounds from shadowing impls when normalizing associated types. There are no known issues from preferring impls over global where-bounds.
 
 #### Why still consider global where-bounds