From f6a197a9b1086e1be9065584f544b27c3eafa133 Mon Sep 17 00:00:00 2001
From: u203965 <marc.walter@sbb.ch>
Date: Thu, 24 Aug 2017 17:55:22 +0200
Subject: [PATCH] fix broken link to Twitter REST API documentation

---
 lessons/restfulresourcenaming.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lessons/restfulresourcenaming.html b/lessons/restfulresourcenaming.html
index 16edf03..8e8e28a 100644
--- a/lessons/restfulresourcenaming.html
+++ b/lessons/restfulresourcenaming.html
@@ -115,7 +115,7 @@
 							<p>By now you can see how the hierarchy concept works. There aren't any hard and fast rules, only make sure the imposed structure makes sense to consumers of your services. As with everything in the craft of Software Development, naming is critical to success.</p>
 							<p>Look at some widely used APIs to get the hang of this and leverage the intuition of your teammates to refine your API resource URIs. Some example APIs are:</p>
 							<ul>
-								<li>Twitter: https://dev.twitter.com/docs/api</li>
+								<li>Twitter: https://dev.twitter.com/overview/api</li>
 								<li>Facebook: http://developers.facebook.com/docs/reference/api/</li>
 								<li>LinkedIn: https://developer.linkedin.com/apis</li>
 							</ul>