The intro may give an impression that Rust has less control about moving values than C, but that's not accurate. The problem is that both languages behave exactly the same: they can pass and assign structs by value, which changes their address.
In C any problems caused by this are "solved" just by telling programmers not to do that. In Rust that's not good enough — safety guarantees are supposed to catch such violations, so the goal is to automatically and robustly prevent incorrect struct moves. Rust already makes that safe by default when using the borrow checker, but it doesn't have a nice built-in mechanism for preventing moves of non-borrowed structs.