Copy types are implicitly cloned whenever they're moved, but because of the definition of Copy this just means not treating the old copy as uninitialized -- a no-op.
I can't understand "-- a no-op". Which action becomes no-op?
I think what it’s saying is that operations that trigger a copy of a Copy trait would be a move for non-Copy types, which also copies the bytes. The only difference is that, in the move case, the compiler makes the old location inaccessible to your code.