docs(dependency pinning): drop reference to motto (#27746)

docs/usage/dependency-pinning.md

@@ -186,7 +186,7 @@ You could even be running `yarn upgrade` regularly to be getting _indirect_ pack
 So the lock file does not solve the same SemVer problems that pinning solves - but it compliments it.
 For this reason our usual recommendation is using a lock file regardless of whether you pin dependencies or not, and pinning even if you have a lock file.
 
-Don't forget though that our motto is "Flexible, so you don't need to be", so go ahead and configure however you want.
+But you may also go ahead and configure however you want.
 Also, we're open to ideas for how to make lock file updates more "visible" too.
 e.g. are you interested in a Renovate feature where you get a lockfile-only PR any time a direct dependency gets an in-range update?