diff --git a/.changeset/green-carrots-trade.md b/.changeset/green-carrots-trade.md
new file mode 100644
index 000000000..a845151cc
--- /dev/null
+++ b/.changeset/green-carrots-trade.md
@@ -0,0 +1,2 @@
+---
+---
diff --git a/docs/config-file-options.md b/docs/config-file-options.md
index 75c893563..eb4f0c257 100644
--- a/docs/config-file-options.md
+++ b/docs/config-file-options.md
@@ -100,7 +100,7 @@ If you want to use this option, you should read the documentation on [linked pac
 
 ## `updateInternalDependencies`
 
-This option sets whether, when a package that is being dependend upon changes, whether you should update what version it depends on. To make this more understandable, here is an example:
+This option sets whether, when a package that is being depended upon changes, whether you should update what version it depends on. To make this more understandable, here is an example:
 
 Say we have two packages, one depending on the other:
 
diff --git a/docs/fixed-packages.md b/docs/fixed-packages.md
index d33354977..a71f8564e 100644
--- a/docs/fixed-packages.md
+++ b/docs/fixed-packages.md
@@ -32,7 +32,7 @@ I now have another changeset with a minor for `pkg-a` and I do a release, the re
 
 ## Using glob expressions
 
-Sometimes you want to fix many or all packages within your project (for example in a monorepository setup), in which case you would need to keep the list of fixed packages up-to-date.
+Sometimes you want to fix many or all packages within your project (for example in a monorepo setup), in which case you would need to keep the list of fixed packages up-to-date.
 
 To make it simpler to maintain that list, you can provide glob expressions in the list that would match and resolve to all the packages that you wish to include.
 
diff --git a/docs/intro-to-using-changesets.md b/docs/intro-to-using-changesets.md
index c66cb0c65..31c5696fd 100644
--- a/docs/intro-to-using-changesets.md
+++ b/docs/intro-to-using-changesets.md
@@ -56,7 +56,7 @@ yarn changeset version
 
 This consumes all changesets, and updates to the most appropriate semver version based on those changesets. It also writes changelog entries for each consumed changeset.
 
-We recommend at this step reviewing both the changelog entries and the version changes for packages. Once you are confident that these are correct, and have made any necessary tweeks to changelogs, you can publish your packages:
+We recommend at this step reviewing both the changelog entries and the version changes for packages. Once you are confident that these are correct, and have made any necessary tweaks to changelogs, you can publish your packages:
 
 ```shell
 npx changeset publish
diff --git a/docs/linked-packages.md b/docs/linked-packages.md
index 08829a200..bf648beb2 100644
--- a/docs/linked-packages.md
+++ b/docs/linked-packages.md
@@ -72,7 +72,7 @@ I now have another changeset with a major for `pkg-a` and I do a release, the re
 
 ## Using glob expressions
 
-Sometimes you want to link many or all packages within your project (for example in a monorepository setup), in which case you would need to keep the list of linked packages up-to-date.
+Sometimes you want to link many or all packages within your project (for example in a monorepo setup), in which case you would need to keep the list of linked packages up-to-date.
 
 To make it simpler to maintain that list, you can provide glob expressions in the linked list that would match and resolve all the packages you wish to include.
 
diff --git a/packages/apply-release-plan/README.md b/packages/apply-release-plan/README.md
index 5d02f1f7a..3d630d446 100644
--- a/packages/apply-release-plan/README.md
+++ b/packages/apply-release-plan/README.md
@@ -22,4 +22,4 @@ await applyReleasePlan(
 
 Note that `apply-release-plan` does not validate the release plan's accuracy.
 
-To generate a releace plan from written changesets use `@changesets/get-release-plan`
+To generate a release plan from written changesets use `@changesets/get-release-plan`
diff --git a/packages/get-github-info/README.md b/packages/get-github-info/README.md
index e54ba3ee7..9464a12b4 100644
--- a/packages/get-github-info/README.md
+++ b/packages/get-github-info/README.md
@@ -35,7 +35,7 @@ const getReleaseLine = async (changeset, type) => {
   // getInfo exposes the GH username and PR number if you want them directly
   // but it also exposes a set of links for the commit, PR and GH username
   let { user, pull, links } = await getInfo({
-    // replace this will your own repo
+    // replace this with your own repo
     repo: "Noviny/changesets",
     commit: changeset.commit,
   });
diff --git a/packages/get-release-plan/README.md b/packages/get-release-plan/README.md
index 58dd98f0c..33afba58d 100644
--- a/packages/get-release-plan/README.md
+++ b/packages/get-release-plan/README.md
@@ -16,9 +16,9 @@ The directory to run `getReleasePlan` in - most often `process.cwd()`
 
 ## since: string
 
-Sets whether to use all changests present, or only those changesets that are new since the branch
+Sets whether to use all changesets present, or only those changesets that are new since the branch
 diverged from another one.
 
 ## passedConfig?: Config
 
-The changeset config options as defined in `@changesets/types`. This is optional, and can be used to overrwrite any written config options.
+The changeset config options as defined in `@changesets/types`. This is optional, and can be used to overwrite any written config options.
diff --git a/packages/logger/README.md b/packages/logger/README.md
index 3e9148e63..55c600d00 100644
--- a/packages/logger/README.md
+++ b/packages/logger/README.md
@@ -38,5 +38,5 @@ temporarilySilenceLogs();
 log("I am not logged");
 
 // Use console.log to log messages in tests if required
-console.log("Yiey, I am logged");
+console.log("Yay, I am logged");
 ```