Fix links to papers that were broken on the website (#1042)

docs/blog/posts/last-week-in-pony-031923.md

@@ -44,7 +44,7 @@ And if it doesn't sound interesting, you can join and steer the conversation in
 
 We like to take a moment in each Last Week in Pony to highlight a community resource. There are many community resources that can go unappreciated until _just the right time_ when someone hops into the Ponylang Zulip asking a question or facing a problem we have all had at one time or another. Well here in Last Week in Pony, we make it **just the right time** to highlight one of our excellent community resources.
 
-This week we are highlighting the [Papers](https://www.ponylang.io/community/#papers) portion of the Pony website! Specifically, we are going to look at [ORCA: GC and Type System Co-Design for Actor Languages](https://www.ponylang.io/media/papers/orca_gc_and_type_system_co-design_for_actor_languages.pdf). This 2017 paper discusses ORCA or Ownership and Reference Counting-based garbage collection in the Actor World -- it may be a bit of a force acronym, but it is a killer whale of a reason to use Pony!
+This week we are highlighting the [Papers](https://www.ponylang.io/learn/papers/) portion of the Pony website! Specifically, we are going to look at [ORCA: GC and Type System Co-Design for Actor Languages](https://www.ponylang.io/media/papers/orca_gc_and_type_system_co-design_for_actor_languages.pdf). This 2017 paper discusses ORCA or Ownership and Reference Counting-based garbage collection in the Actor World -- it may be a bit of a force acronym, but it is a killer whale of a reason to use Pony!
 
 The entire paper is worth a read, but here we want to highlight the invariants list from section 4.1 that ORCA maintains:
 

docs/blog/posts/last-week-in-pony-070223.md

@@ -35,7 +35,7 @@ Normally we have a monthly release of `ponyc`. However, there's not really any c
 
 We like to take a moment in each Last Week in Pony to highlight a community resource. There are many community resources that can go unappreciated until _just the right time_ when someone hops into the Ponylang Zulip asking a question or facing a problem we have all had at one time or another. Well here in Last Week in Pony, we make it **just the right time** to highlight one of our excellent community resources.
 
-This week we are going to look at one of the papers available at <https://www.ponylang.io/community/#papers> -- specifically we are going to look at [A String of Ponies](https://www.ponylang.io/media/papers/a_string_of_ponies.pdf)!
+This week we are going to look at one of the papers available at <https://www.ponylang.io/learn/papers/> -- specifically we are going to look at [A String of Ponies](https://www.ponylang.io/media/papers/a_string_of_ponies.pdf)!
 
 This paper is focused on all aspects of what it would take to go from the Concurrent Pony of today to full-fledged Distributed Pony! It is well worth a full read, but today let's focus on Distributed Pony [Termination](https://www.ponylang.io/media/papers/a_string_of_ponies.pdf#section.3.8). As a reminder, Pony today terminates when it has reached a state of _quiescence_ whereby there is no remaining work (see [When do programs exit?](https://www.ponylang.io/faq/runtime/#program-exit) for more information). This presents a major problem in a distributed environment: how do we differentiate between locally running out of work and globally running out of work? This is far from easy to fix. This section includes two attempts at designing a solution, the first is broken while the second work. As with many aspects of Pony, the working solution leverages message causality. By defining a _termination detector_ and leveraging Pony's existing causal messaging we can identify when to terminate the program. The result of this emphasis on causal messaging in a distributed system is a tree network topology -- the chapter that directly follows from Termination, investigating this topic further is left as a exercise to the reader!
 

docs/blog/posts/last-week-in-pony-091017.md

@@ -16,7 +16,7 @@ Got something you think should be featured? There's a GitHub issue for that! Add
 ## Items of note
 
 - Yesterday, Sean T. Allen created a starter kit for Pony library projects. The project is available at [https://github.com/ponylang/library-project-starter](https://github.com/ponylang/library-project-starter). Full details on features is available in its USAGE.md.
-- Academic papers relating to Pony are back on the website after a long absence. Currently, they live in the [community section](https://www.ponylang.io/community/#papers) of the website.
+- Academic papers relating to Pony are back on the website after a long absence. Currently, they live in the [community section](https://www.ponylang.io/learn/papers/) of the website.
 
 - Audio from the [September 6, 2017, Pony development sync](https://vimeo.com/915150905) is available for your listening pleasure.
 

docs/blog/posts/last-week-in-pony-10292017.md

@@ -25,7 +25,7 @@ Got something you think should be featured? There's a GitHub issue for that! Add
 
 - The Pony development sync audio from last week is available right [here](https://vimeo.com/915352960), right now! Amongst other stuff it features Sylvan sharing pretty exciting ideas about the future of the Pony GC and thus the type system itself.
 
-- George Steed's Thesis "A Principled Design of Capabilities in Pony" is now available in the Papers section of the Pony website as well: [https://www.ponylang.io/community/#papers](https://www.ponylang.io/community/#papers). Last year George did a Virtual Users' Group presentation on his thesis as well: [https://vimeo.com/178522513](https://vimeo.com/178522513)
+- George Steed's Thesis "A Principled Design of Capabilities in Pony" is now available in the Papers section of the Pony website as well: [https://www.ponylang.io/learn/papers/](https://www.ponylang.io/learn/papers/). Last year George did a Virtual Users' Group presentation on his thesis as well: [https://vimeo.com/178522513](https://vimeo.com/178522513)
 
 ## RFCs