From caec8df08397c870f69ad2fd101a1c4d31b654eb Mon Sep 17 00:00:00 2001
From: infominer33 <44134283+infominer33@users.noreply.github.com>
Date: Tue, 18 Dec 2018 00:39:23 -0500
Subject: [PATCH] Update user-experience.md

---
 self-sovereign/user-experience.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/self-sovereign/user-experience.md b/self-sovereign/user-experience.md
index d14c123d..bf9aa498 100644
--- a/self-sovereign/user-experience.md
+++ b/self-sovereign/user-experience.md
@@ -1,5 +1,5 @@
 # How would self-sovereign identity work for the user?
-Adapted from [A gentle introduction to self-sovereign-identity](https://bitsonblocks.net/2017/05/17/gentle-introduction-self-sovereign-identity/) by @antonylewis. I think this could use some polishing, but this is a good start, and a good example of a basic necessary SSI explainer.
+Adapted from [A gentle introduction to self-sovereign-identity](https://bitsonblocks.net/2017/05/17/gentle-introduction-self-sovereign-identity/) by [@antonylewis](https://github.com/antonylewis). I think this could use some polishing, but this is a good start, and a good example of a basic necessary SSI explainer.
 
 You would have an app on a smartphone or computer, some sort of “identity wallet” where identity data would be stored on the hard drive of your device, or with an agent of your choosing, but crucially not stored in a central repository.