Add some additional source issue information.

docs/2.3-Distributing-GitHub.md

@@ -23,6 +23,8 @@ Task task = Task.Run(async () =>
{
    using (var mgr = UpdateManager.GitHubUpda
     using (var mgr = UpdateManager.GitHubUpdateManager("https://github.com/myuser/myapp"))
     {
         await mgr.Result.UpdateApp();
+    }
+});
 ~~~
 
 **Tip:** You can also specify that the update manager should use `prerelease` for updating (see method signature for details).

docs/2.4-Machine-wide-Installs.md

@@ -15,6 +15,8 @@ Most users of Squirrel won't have to do anything new to enable this behavior, th
 PM> Squirrel --releasify MyApp.1.0.0.nupkg --no-msi
 ~~~ 
 
+**Source:** See [issue #466](https://github.com/Squirrel/Squirrel.Windows/issues/466) for more details.
+
 ---
 | Return: [2.4 More Installing](2.4-More-Installing.md)|
 |----|

docs/2.5-More-Updating.md

@@ -11,7 +11,7 @@ You can't. So, how can you do it? The basic trick that ClickOnce uses is, you ha
 
 ## Detailed Updating Process
 
-The following steps are performed by the `UpdateManager` each time MyApp is executed (see [2.5 More Updating](2.5-More-Updating.md) for details):
+The following steps are performed by the `UpdateManager` each time MyApp is executed:
 
 1. **Check for Updates** - the `RELEASES` file at the distribution location is downloaded and compared to local `RELEASES` file to check for any updates.
 2. **Download & Verify Update Packages** - if there is a new release, the `UpdateManager` determines whether to download the deltas or the latest full package to update to the current version. The packages are compared against their SHA1 in the `RELEASES` file for verification.