diff --git a/guide/english/agile/user-stories/index.md b/guide/english/agile/user-stories/index.md
index 7fe1331531..150ef8aaa2 100644
--- a/guide/english/agile/user-stories/index.md
+++ b/guide/english/agile/user-stories/index.md
@@ -19,6 +19,8 @@ It also reduces the time and effort required to integrate new insights. If you h
 
 When thinking about possible stories, it is also important to consider "mis-user cases" and "unhappy path" stories.  How will exceptions be handled by the system?  What kind of messaging will you provide back to user?  How would a malicious user abuse this application function?  These mal-stories can save rework and become usful test cases in QA.
 
-#### More Information:
+#### More Information
 - <a href='https://www.mountaingoatsoftware.com/agile/user-stories' target='_blank' rel='nofollow'>Mountain Goat Software Guide to User Stories</a>
 - <a href='http://www.romanpichler.com/blog/10-tips-writing-good-user-stories/' target='_blank' rel='nofollow'>Roman Pichler Guide to User Stories</a>
+- <a href='https://blog.easyagile.com/how-to-write-good-user-stories-in-agile-software-development-d4b25356b604' target='_blank' rel='nofollow'>How to Write Good User Stories in Agile Software Development</a>
+- <a href='https://www.coursera.org/lecture/uva-darden-getting-started-agile/coaching-for-better-user-stories-EV2FE' target='_blank' rel='nofollow'>Coursera course for better User Stories</a>