docs: Update getting started wizard with additionl information

doc/articles/get-started-wizard.md

@@ -116,5 +116,18 @@ You can migrate your WSL v2 installation into a v1, by [visiting this document](
 #### Abnormally long build times when using Roslyn analyzers
 It is a good practice to use Roslyn analyzers to validate your code during compilation, but some generators may have difficulty handling the source generated by the Uno Platform (one notable example is [GCop](https://github.com/Geeksltd/GCop)). You may need to disable those for Uno projects or get an update from the analyzer's vendor.
 
-#### XAML Hot Reload for the UWP head may not work properly in Visual Studio 2019 16.7 and earlier
-The [XAML Hot Reload](https://docs.microsoft.com/en-us/visualstudio/xaml-tools/xaml-hot-reload?view=vs-2019) feature [does not work in Visual Studio 2019 16.7](https://developercommunity.visualstudio.com/content/problem/996417/xaml-hot-reload-hot-reload-is-not-working-in-share.html) and earlier for Uno projects. This has been fixed in 16.8 and later.
+#### XAML Hot Reload troubleshooting
+
+The XAML Hot reload provides a Visual Studio for Windows output window name "Uno Platform" with diagnotics messages. You can find additional information there in case XAML Hot Reload does not work properly.
+
+Some common troubleshooting steps:
+- Make sure to rebuild your application if the XAML changes are not applied
+- Ensure that the Uno.UI.RemoteControl package has the same version as the Uno.UI package (Similar step is valid for Uno.WinUI packages)
+
+More troubleshooting information is available [in this section](features/working-with-xaml-hot-reload.md).
+
+##### WebAssembly: Hot Reload fails to start with Mixed Content: The page at XXX was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint
+
+This issue is caused by visual studio enforcing https connections for local content. You can work around this by either:
+- Removing the https endpoint in the `Properties/launchSettings.json` file
+- Selecting the project name instead of IISExpress in the toolbar debug icon drop down list