Fix Helm character limit in migration guide

docs/docs/user/migration-guide/v2-v3.md

@@ -4,12 +4,12 @@
 
 KPOps handles long (more than 53 characters) Helm releases names differently. Helm will not find your (long) old release names anymore. Therefore, it is recommended that you should once destroy your pipeline with KPOps v2 to remove old Helm release names. After a clean destroy, re-deploy your pipeline with the KPOps v3.
 
-For example if you have a component with the Helm release name `example-component-name-too-long-fake-fakefakefakefakefake`. The new release name will shorten the original name to 52 characters and then replace the last 6 characters of the trimmed name with the first 5 characters of the result of SHA-1(helm_release_name).
+For example if you have a component with the Helm release name `example-component-name-too-long-fake-fakefakefakefakefake`. The new release name will shorten the original name to 53 characters and then replace the last 6 characters of the trimmed name with the first 5 characters of the result of SHA-1(helm_release_name).
 
 <!-- dprint-ignore-start -->
 
 ```console
-example-component-name-too-long-fake-fakefakef-0a7fc ----> 52 chars
+example-component-name-too-long-fake-fakefakef-0a7fc ----> 53 chars
 ---------------------------------------------- -----
   ^Shortened helm_release_name                 ^first 5 characters of SHA1(helm_release_name)
 ```