docs: update Nx page on dependency recommendations (#10034)

### Description

Pulling [this
suggestion](#10003 (comment))
over to a separate PR to make sure it gets in since [the original
PR](#10003) was closed.
@JamesHenry confirmed this is the case, so wanting to make sure we're
accurate!

Author: anthonyshew

docs/repo-docs/guides/migrating-from-nx.mdx

@@ -439,7 +439,7 @@ We encourage incremental migration, meaning you will have both of Nx and Turbore
 
 Turborepo recommends [installing packages where they're used](/repo/docs/crafting-your-repository/managing-dependencies#best-practices-for-dependency-installation) to improve cache hit ratios, help dependency pruning capability, and clarify for developers which dependencies are meant for which packages. This is different from the Nx strategy, where all dependencies are installed at the root of the repository, making all dependencies available to all packages in the workspace.
 
-Once you have tasks running through Turborepo, we highly recommend that you move dependencies to the `package.json`'s for packages and applications that need them. [Visit our documentation on managing dependencies](/repo/docs/crafting-your-repository/managing-dependencies) to learn more.
+Historically, Nx has recommended installing all dependencies in the root of the repository, making all dependencies available to all packages in the Workspace. If you followed this guidance, we highly recommend that you move dependencies to the `package.json`'s for packages and applications that need them. [Visit our documentation on managing dependencies](/repo/docs/crafting-your-repository/managing-dependencies) to learn more.
 
 ### Creating shared packages