No support ticket required. Thanks for letting us know.
Correcting the typo in the parameter won't be possible that easy. It would break a lot of existing scripts.
But we will check what we can do for a future release.
Thanks for your feedback. Yes, unfortunately, there is quite a set of cmdlets and classes with typos in their parameter and property names. Most of them are old though (Start-VBRQuickMigration is one of them). With newer types we have been doing our best to review the spelling more thoroughly. I do think, however, that there is always a space for improvement, but not to the point where we need to create a new parameter with the same purpose as the older one just for the sake of correct spelling. It's just too much of an overhead to apply deprecation workflows here and make users rewrite their existing scripts.