fixing broken links

mattmakai · mattmakai · commit 5187a35a2faa · 2021-06-01T20:21:01.000-04:00
diff --git a/content/pages/meta/00-change-log.markdown b/content/pages/meta/00-change-log.markdown
@@ -14,6 +14,10 @@ view commit-level changes via the
 on GitHub.
 
 ## 2021
+### June
+* Fix broken links across the site. It's a real shame people and companies don't use
+  301 redirects more often rather than just breaking their URL structures.
+
 ### May
 * New resources on [GPT-3](/gpt-3.html), [Jupyter Notebook](/jupyter-notebook.html)
   and [serverless](/serverless.html) pages.
diff --git a/content/posts/190626-dev-led-sales-startups.markdown b/content/posts/190626-dev-led-sales-startups.markdown
@@ -456,9 +456,9 @@ tactics.
 </div><div class="c6"><p>
 Conferences split into a couple of categories: community-run and
 vendor-run. For example, 
-<a href="https://developer.apple.com/wwdc19/">WWDC</a> is Apple's vendor-run
+<a href="https://developer.apple.com/wwdc/">WWDC</a> is Apple's vendor-run
 developer conference. They run the show and control the messaging.
-<a href="https://us.pycon.org/2019/">PyCon US</a> is the community-run 
+<a href="https://us.pycon.org/">PyCon US</a> is the community-run 
 Python developer conference. There are a ton of vendors there as sponsors
 but no one company controls what happens at the conference.
 </p><p>
diff --git a/content/posts/200630-report-errors-flask-web-apps-sentry.markdown b/content/posts/200630-report-errors-flask-web-apps-sentry.markdown
@@ -260,5 +260,5 @@ or [@mattmakai](https://twitter.com/mattmakai). I am also on GitHub with
 the username [mattmakai](https://github.com/mattmakai).
 
 If you see an issue or error in this tutorial, please
-[fork the source repository on GitHub](https://github.com/mattmakai/fullstackpython/blob/master/content/posts/200630-report-errors-flask-web-apps-sentry.markdown)
+[fork the source repository on GitHub](https://github.com/mattmakai/fullstackpython.com/blob/master/content/posts/200630-report-errors-flask-web-apps-sentry.markdown)
 and submit a pull request with the fix.
