Update docs to reflect new framer-motion addition

Editor assessment

The subject states the purpose: documentation was updated to reflect the addition of framer-motion. The dependency being documented is named, so the reader knows the catalyst for the docs churn. The docs type matches. No scope is present, tolerable for a broad documentation sync whose subject names the driver. There is no body, acceptable for a straightforward alignment change whose headline carries the reason. No footers appear. The doubled docs wording is slightly redundant, a minor note on a clear message.