1. add a note that copy content feature might be called cloning and extend information basing on the comment from Jan below (eg. not changing IDs)
2. Add information about custom workspaces of content apps (it was a question from a partner , if they have custom workspaces for content apps, if the content will also be copied)

Comment from Jan in PD- Cloud room:
"there was feature for copying content in old alfresco. and those who have used it remember it being slow, error prone and potentially disastrous (when amount of free data-scheme in db was lower than size of the copy it filled up the schema and corrupted original data too). for that reason (and few others like IDs are not changing, etc), I'd prefer to call the operation always cloning to avoid negative connotations/rememberance and to be clear in regard what the op does"