When moving or renaming, pages or documents get deactivated immediately (which shouldn't be the case, really, but that's a larger task). The user at least gets a warning about this, except if the node's status was not "activated". Unfortunately, the deactivation still occurs in any case, so nodes get silently deactivated on public instances (this happens for instance with samples or bootstrap content which is not marked as activated, even though it somehow is in synch between the instances)