From ae71c04f0010aecbf2aa386f92334396578e91a7 Mon Sep 17 00:00:00 2001
From: Kyle Tsang <6854874+kyletsang@users.noreply.github.com>
Date: Tue, 28 Dec 2021 18:22:33 -0800
Subject: [PATCH] docs: fix typo in migrate-from-lerna.mdx

---
 docs/pages/docs/guides/migrate-from-lerna.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/pages/docs/guides/migrate-from-lerna.mdx b/docs/pages/docs/guides/migrate-from-lerna.mdx
index 211a46aeeb440..99902e34971ec 100644
--- a/docs/pages/docs/guides/migrate-from-lerna.mdx
+++ b/docs/pages/docs/guides/migrate-from-lerna.mdx
@@ -27,7 +27,7 @@ The above may not not look like much. But imagine that A's `build` task takes 20
 
 ### Package Publishing, Versioning, and Changelog Generation
 
-Lerna can version and publish packages to NPM registries as well as create changelogs. It's extremely good at this, especially for releasing canary pre-releases. While Turborepo may eventually tackle these features, at the time of writing, it is not a high priority goal (we suggest using using [Changesets](https://github.com/changesets/changesets) in the meantime). If Changesets isn't for you, and you want to stick with Lerna's publish flow, you can use Lerna and Turborepo together.
+Lerna can version and publish packages to NPM registries as well as create changelogs. It's extremely good at this, especially for releasing canary pre-releases. While Turborepo may eventually tackle these features, at the time of writing, it is not a high priority goal (we suggest using [Changesets](https://github.com/changesets/changesets) in the meantime). If Changesets isn't for you, and you want to stick with Lerna's publish flow, you can use Lerna and Turborepo together.
 
 ## Example migration