From fcf5b9cec39cd930f1307fc9da5b2e0bb0740ea3 Mon Sep 17 00:00:00 2001 From: Riccardo Di Maio <35903974+rdimaio@users.noreply.github.com> Date: Sun, 17 Sep 2023 12:40:31 +0100 Subject: [PATCH] docs(core): Typo fix (#19205) --- docs/shared/migration/adding-to-monorepo.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/shared/migration/adding-to-monorepo.md b/docs/shared/migration/adding-to-monorepo.md index aea0133b8f..40912f8457 100644 --- a/docs/shared/migration/adding-to-monorepo.md +++ b/docs/shared/migration/adding-to-monorepo.md @@ -69,7 +69,7 @@ It also creates a `nx.json` based on the answers given during the setup process. ## Incrementally Adopting Nx -In a package-based monorepo, Nx only manages the scheduling and caching of your npm scripts. Hence, it can easily be adopt incrementally by initially using Nx just for a subset of your scripts and then gradually adding more. +In a package-based monorepo, Nx only manages the scheduling and caching of your npm scripts. Hence, it can easily be adopted incrementally by initially using Nx just for a subset of your scripts and then gradually adding more. For example, use Nx to run your builds: