fix(migration.v6): correct fragment links in migration v6 guide (#394)

During the change in #373 , the v6 migration guide was not fully updated
with the new fragment links.

This PR fixes that.

Author: stijnmoreels

versioned_docs/version-v6.0.0/support/v6-migration.md

@@ -192,8 +192,8 @@ It is also possible to use the auto created Invictus for Azure user assigned man
 We need to replace the following components with the new containerized API's. 
 
 * [Migrating PubSub v1 to v2](../framework/pubsubV2.md#migrating-pubsub-v1-to-v2)
-* [Migrating Transco v1 to v2](../framework/transcoV2.mdx#migrating-transco-v1-to-v2)
-* [Migrating Matrix v1 to Transco v2](../framework/transcoV2.mdx#migrating-matrix-v1-to-transco-v2)
+* [Migrating Transco v1 to v2](../framework/transcoV2.mdx#migrating-v1-to-v2)
+* [Migrating Matrix v1 to Transco v2](../framework/transcoV2.mdx#migrating-v1-to-v2)
 
 ## Common Migration Issues
 :::danger[pipeline error: `Operating system not supported`]
@@ -202,4 +202,4 @@ Your release pipeline agent must be a linux agent, for example `vmImage: 'ubuntu
 
 :::danger[Pipeline Error: `Invalid ContainerApp name....The length must be between 2 and 32 characters inclusive.`]
 If you are overriding the default app names, the provided name might be too long, as the Container App name limit is lower than for function apps.
-:::
+:::