From a7b37780f44eec83d5ea33d841cc67d4e0f8385c Mon Sep 17 00:00:00 2001 From: James Pulec Date: Sat, 3 Sep 2022 14:11:19 -0700 Subject: [PATCH] docs: fix small grammar error (#4792) Update release-workflow.md --- packages/gatsby/content/features/release-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/gatsby/content/features/release-workflow.md b/packages/gatsby/content/features/release-workflow.md index 2a51db24a4c5..6e7d92f9fe39 100644 --- a/packages/gatsby/content/features/release-workflow.md +++ b/packages/gatsby/content/features/release-workflow.md @@ -37,7 +37,7 @@ In pre-2.0, upgrading `common` would have required you to run the command there, /packages/client (depends on common@^1.1.1) ``` -Of course it's not that important when the packages from the monorepo are always meant to be used as part of the monorepo, but it becomes much more interesting when you work with multiple packages meant to be published. Have you forgotten to update the range of either of your dependent packages, your users would have potentially downloaded an old version of `common` which wouldn't have been compatible with the newer one. +Of course it's not that important when the packages from the monorepo are always meant to be used as part of the monorepo, but it becomes much more interesting when you work with multiple packages meant to be published. Had you forgotten to update the range of either of your dependent packages, your users would have potentially downloaded an old version of `common` which wouldn't have been compatible with the newer one. ## Deferred versioning