spelling

docs/contentctl_v5_migration_guide.md

@@ -4,7 +4,7 @@ There are some BIG changes with the v5.0 release of `contentctl` that we think y
 
 ### Strict Fields
 
-Over the years, the YAML files we track our content in have had a lot of different fields in them. There have been varying levels of success when it comes to removing the fields that were no longer necessary, which lead to fields that didn't do anything sticking around. This is no longer the case. We've tweaked the settings on the classes to no longer allow extra fields. This will likely create a small pile of work in order to remove them. Common legacy fields within our own content were `datamodel`, `dataset`, as well as some of the fields we've removed as part of the other updates detailed below. You can run `contentctl validate` with a v5.0+ build and get the validation errors for each and every file. The errors messages will describe what the error is, such as "Extra inputs are not permitted":
+Over the years, the YAML files we track our content in have had a lot of different fields in them. There have been varying levels of success when it comes to removing the fields that were no longer necessary, which lead to fields that didn't do anything sticking around. This is no longer the case. We've tweaked the settings on the classes to no longer allow extra fields. This will likely create a small pile of work in order to remove them. Common legacy fields within our own content were `datamodel`, `dataset`, as well as some of the fields we've removed as part of the other updates detailed below. You can run `contentctl validate` with a v5.0+ build and get the validation errors for each and every file. The error messages will describe what the error is, such as "Extra inputs are not permitted":
 
 ![a terminal emulator screenshot of a validation error caused by extra fields](validation_error.png)