minor update to clickonce to fix link

Author: caesay

docs/migrating/clickonce.mdx

@@ -16,7 +16,7 @@ We will need to start by publishing your first Velopack release.
 1. If you are using any of the `ApplicationDeployment` API's to check for updates, you will need to remove them.
 0. Turn off ClickOnce updates in your project settings, then manually open the `.csproj` and remove all ClickOnce related properties.
    :::tip
-   If you are still on the legacy msbuild/csproj format, you should consider migrating to the SDK style project using the [dotnet/upgrade-assistant](https:// github.com/dotnet/upgrade-assistant) (The [VS extension](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) is easy to  use). You can continue to use .Net Framework, and the legacy csproj format may work however is not officially supported by Velopack.
+   If you are still on the legacy msbuild/csproj format, you should consider migrating to the SDK style project using the [dotnet/upgrade-assistant](https://github.com/dotnet/upgrade-assistant) (The [VS extension](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) is also very easy to use). You can continue to use .Net Framework, and the legacy csproj format may work, however is not officially supported by Velopack so an upgrade is recommended.
    :::
 0. Follow the [Velopack C# QuickStart](../getting-started/csharp.mdx) guide and/or review the samples to add Velopack updates to your application.
 0. Your first install of Velopack should uninstall your ClickOnce app. Ideally we would just run the default uninstaller, but since it cant be used unattended/silent, we need to include the [Wunder.ClickOnceUninstaller](https://github.com/rongchunzhang/Wunder.ClickOnceUninstaller) code. It is not currently distributed on NuGet, so you may wish to download and include the code directly in your project.