diff --git a/migrations/migrate-to-version-6.md b/migrations/migrate-to-version-6.md
index 8b40e815..c246cbdd 100644
--- a/migrations/migrate-to-version-6.md
+++ b/migrations/migrate-to-version-6.md
@@ -16,6 +16,6 @@ module.exports = {
 };
 ```
 
-However, while the it's still a pre-release, the underlying schemas CAN contain breaking changes from version to version, up until the AsyncAPI specification is released. This means that one AsyncAPI document using v3 in the pre-release stage might be valid in `6.0.0`, but invalid in the `6.1.0`. This ONLY applies to pre-release schemas, and NOT regular ones that is set in stone.
+However, while it's still a pre-release, the underlying schemas CAN contain breaking changes from version to version, up until the AsyncAPI specification is released. This means that one AsyncAPI document using v3 in the pre-release stage might be valid in `6.0.0`, but invalid in the `6.1.0`. This ONLY applies to pre-release schemas, and NOT regular ones that are set in stone.
 
 If you want to make sure you don't use a schema not released yet, you have to whitelist which versions you allow in your tool.
\ No newline at end of file