Clean up links and redirects

Author: caesay

docs/getting-started/fusion-cli.mdx

@@ -25,7 +25,7 @@ These are the possible outputs:
 - **Unrecoverable error:** empty stdout and `exitCode != 0`. A [log file](#logging) will be created.
 - **Update is availble:** stdout contains json object and `exitCode == 0`.
 
-When an update is available, you'll receive an [UpdateInfo](../reference/cs/Velopack/UpdateInfo.md) object via stdout:
+When an update is available, you'll receive an [UpdateInfo](../reference/cs/Velopack/UpdateInfo) object via stdout:
 
 ```json
 {

docs/integrating/hooks.mdx

@@ -3,7 +3,7 @@
 
 Hooks allow your application to run logic at various stages of the install/update/uninstall process.
 
-In general, I don't recommend trying to handle hooks manually - and instead refer to the available [VelopackApp](../reference/cs/Velopack/VelopackApp.md) options.
+In general, I don't recommend trying to handle hooks manually - and instead refer to the available [VelopackApp](../reference/cs/Velopack/VelopackApp) options.
 
 If you wish to handle these yourself, an SDK doesn't exist for your language, or you just want to learn more about it, read on.
 

docs/integrating/overview.mdx

@@ -40,14 +40,14 @@ static void Main(string[] args)
 }
 ```
 
-The full list of options [for VelopackApp is available here](../reference/cs//Velopack/VelopackApp.md). You can also read more about [how hooks work](./hooks.mdx).
+The full list of options [for VelopackApp is available here](../reference/cs/Velopack/VelopackApp). You can also read more about [how hooks work](./hooks.mdx).
 
 :::warning
 A "FastCallback" requires that your application show no UI and exit quickly. When the callback returns, your application will exit. If you do not exit this callback quickly enough your process will be killed.
 :::
 
 ## Configuring Updates
-Updates can be accomplished by adding [UpdateManager](../reference/cs/Velopack/UpdateManager.md) to your app:
+Updates can be accomplished by adding [UpdateManager](../reference/cs/Velopack/UpdateManager) to your app:
 
 ```cs
 private static async Task UpdateMyApp()
@@ -76,12 +76,12 @@ You can host your update packages basically anywhere, here are a few examples:
 - HTTP server, or S3, Azure Storage, etc:<br/>`new UpdateManager("https://the.place/you-host/updates")`
 - GitHub Releases:<br/>`new UpdateManager(new GitHubSource("https://github.com/yourName/yourRepo")`
 
-There are a variety of built-in sources (eg. [GithubSource](../reference/cs/Velopack.Sources/GithubSource.md), [SimpleWebSource](../reference/cs/Velopack.Sources/SimpleWebSource.md)) you can use when checking for updates, but you can also build your own by [deriving from IUpdateSource](../reference/cs/Velopack.Sources/IUpdateSource.md).
+There are a variety of built-in sources (eg. [GithubSource](../reference/cs/Velopack/Sources/GithubSource), [SimpleWebSource](../reference/cs/Velopack/Sources/SimpleWebSource)) you can use when checking for updates, but you can also build your own by [deriving from IUpdateSource](../reference/cs/Velopack/Sources/IUpdateSource).
 
 ### Check for updates
-`CheckForUpdatesAsync` will read the provided update source for a `releases.{channel}.json` file to retrieve available updates ([Read about channels](../packaging/channels.mdx)). If there is an update available, a non-null [UpdateInfo](../reference/cs/Velopack/UpdateInfo.md) will be returned with some details about the update. You can also [retrieve any release notes](release-notes.mdx) which were provided when the update was packaged.
+`CheckForUpdatesAsync` will read the provided update source for a `releases.{channel}.json` file to retrieve available updates ([Read about channels](../packaging/channels.mdx)). If there is an update available, a non-null [UpdateInfo](../reference/cs/Velopack/UpdateInfo) will be returned with some details about the update. You can also [retrieve any release notes](release-notes.mdx) which were provided when the update was packaged.
 
-There are [also some options](../reference/cs/Velopack/UpdateOptions.md) which can be passed in to [UpdateManager](../reference/cs/Velopack/UpdateManager.md) to customise how updates are handled, eg. to allow things like [switching channels](switching-channels.mdx).
+There are [also some options](../reference/cs/Velopack/UpdateOptions) which can be passed in to [UpdateManager](../reference/cs/Velopack/UpdateManager) to customise how updates are handled, eg. to allow things like [switching channels](switching-channels.mdx).
 
 ### Download updates
 `DownloadUpdatesAsync` will attempt to download deltas (if available) and re-construct the latest full release. If there are no deltas available, or the delta reconstruction fails, the latest full release package will be downloaded instead. Note that if an option like `AllowVersionDowngrade` is specified, the downloaded version might be older than the currently executing version.

docs/troubleshooting/cli.mdx

@@ -29,7 +29,8 @@ new UpdateManager("https://path.to/your-updates", logger: new ConsoleLogger());
 ## Logging in the Velopack binaries
 
 ### Windows
-Running Update.exe will log most output to it's base directory as `Velopack.log`. Setup.exe will not log to file by default. However, you can override the log location for both binaries with the `--log {path}` parameter. You can also use the `--verbose` flag to capture debug/trace output to log. Unfortunately, on Windows, to avoid showing up as a console window, these binaries are compiled as a WinExe and there will be no console output by default.  Please see the [command line reference](cli.mdx) for a comprehensive list of arguments supported.
+Running Update.exe will log most output to it's base directory as `Velopack.log`. Setup.exe will not log to file by default. However, you can override the log location for both binaries with the `--log {path}` parameter. You can also use the `--verbose` flag to capture debug/trace output to log. Unfortunately, on Windows, to avoid showing up as a console window, these binaries are compiled as a WinExe and there will be no console output by default.  
+Please see the [command line reference](../reference/cli) for a comprehensive list of arguments supported.
 
 ### Linux
 All logs will be sent to `/tmp/velopack.log`.

docs/troubleshooting/debugging.mdx

@@ -29,6 +29,7 @@ const config: Config = {
     ['@docusaurus/plugin-client-redirects', {
       redirects: [
         { from: '/packaging/rid', to: '/packaging/runtime' },
+        { from: '/troubleshooting/cli', to: '/reference/cli' },
       ],
     }],
   ],

docusaurus.config.ts

@@ -71,9 +71,10 @@ const sidebars: SidebarsConfig = {
     auto("distributing", "Distributing", "Learn how to distribute your Velopack releases to your users."),
 
     title("Advanced"),
-    auto("troubleshooting", "Troubleshooting", "Debugging steps, common issues and how to resolve them."),
     auto("contributing", "Contributing", "Learn how to contribute to the Velopack project."),
     auto("migrating", "Migrating", "Learn how to migrate your existing application to Velopack."),
+    doc("troubleshooting/debugging", "Debugging & Logging"),
+    doc("troubleshooting/faq", "FAQ"),
   ],
   referenceSidebar: [
     {