From 86b2579658070627280cce516a48d3514b4e0050 Mon Sep 17 00:00:00 2001
From: Ken Bailey <kenbailey@mdsc.com>
Date: Wed, 30 Dec 2015 09:51:54 -0700
Subject: [PATCH] Add some additional source issue information.

---
 docs/2.3-Distributing-GitHub.md   | 2 ++
 docs/2.4-Machine-wide-Installs.md | 2 ++
 docs/2.5-More-Updating.md         | 2 +-
 3 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/2.3-Distributing-GitHub.md b/docs/2.3-Distributing-GitHub.md
index e346660d..abd725cf 100644
--- a/docs/2.3-Distributing-GitHub.md
+++ b/docs/2.3-Distributing-GitHub.md
@@ -23,6 +23,8 @@ Task task = Task.Run(async () =>
{
    using (var mgr = UpdateManager.GitHubUpda
 
 **Tip:** You can also specify that the update manager should use `prerelease` for updating (see method signature for details).
 
+**Source:** See [Issue #442](https://github.com/Squirrel/Squirrel.Windows/issues/442) for more information.
+
 ### Distributing to GitHub
 
 The following steps are required to distribute your update files with GitHub:
diff --git a/docs/2.4-Machine-wide-Installs.md b/docs/2.4-Machine-wide-Installs.md
index 0b4cbf4f..b344e7b5 100644
--- a/docs/2.4-Machine-wide-Installs.md
+++ b/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)|
 |----|
diff --git a/docs/2.5-More-Updating.md b/docs/2.5-More-Updating.md
index 64c1b1b8..e1737de2 100644
--- a/docs/2.5-More-Updating.md
+++ b/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.