Updated broken links

content/blog/april-update-ce-fcc-software-update-and-diy-router.md

@@ -18,10 +18,10 @@ tags:
 cover: 
   image: "header.jpg"
 images:
-  - "/blog/images/header.jpg"
+  - "/blog/images/header_with_pinephone_and_pinebookpro.jpg"
 ---
 
-![](/blog/images/header.jpg)
+![](/blog/images/header_with_pinephone_and_pinebookpro.jpg)
 
 I hope and trust this update finds everyone well. Production in China is picking up pace and we expect to start shipping the Pinebook Pro with Manjaro and PinePhone UBports Community edition next month. I am happy to report that, for the time being, everything is proceeding  smoothly and we’re on track to ship devices in accordance with our original plans. Still, I encourage you to sign up to this blog to stay up-to-date on shipping information since anything can happen in the next 30 days. 
 

content/blog/april-update-no-more-unicorns.md

@@ -85,7 +85,7 @@ It is time for the second community quarterly Q&A. If you’re reading this on t
 
 We have upgraded the [main PINE64](https://app.element.io/#/room/#pine64:matrix.org) and [PinePhone](https://app.element.io/#/room/#pinephone:matrix.org) Matrix channels. Both of them previously ran version 1 of the Matrix protocol and this caused us all sorts of headaches, including moderators randomly losing their powers and people who left being forced back into the home server. Needless to say, an upgrade had to happen sooner or later. The new rooms now run version 6 of the Matrix protocol which will alleviate all the aforementioned problems. An unfortunate side-effect of the upgrade is that everyone who was part of the original channels will need to manually rejoin. An invite link is present in the original groups. 
 
-As some of you noticed, there was no new [PineTalk](https://www.pine64.org/pinetalk/) episode last month. Those involved in the production of the podcast were busy with real-life things and simply didn’t get the chance to record. I’ve spoken to Brian and Justin and they both confirmed that a new episode will be coming later this month. If you haven’t done so yet, make sure to subscribe to [PineTalk’s RSS feed](https://www.pine64.org/feed/mp3/). 
+As some of you noticed, there was no new [PineTalk](https://www.pine64.org/podcast/) episode last month. Those involved in the production of the podcast were busy with real-life things and simply didn’t get the chance to record. I’ve spoken to Brian and Justin and they both confirmed that a new episode will be coming later this month. If you haven’t done so yet, make sure to subscribe to [PineTalk’s RSS feed](https://www.pine64.org/feed/mp3/). 
 
 The product team is in advanced talks with a factory regarding resuming production of the Pinebook Pro. As I’ve promised countless times in the past, I’ll keep you updated on the progress regarding restarting the laptop’s production. I’m told the team is etching closer to strike a deal and that the production circumstances will require some alterations to parts of the hardware - keep an eye on our social media and news channels in the coming weeks.
 
@@ -167,7 +167,7 @@ In other news, the [documentation of the PinePhone Pro](https://wiki.pine64.org/
 
 **A functionality matrix has been added to the [PinePhone Pro Wiki](https://wiki.pine64.org/wiki/PinePhone_Pro) section**
 
-The software section of the PinePhone Pro article, which was extended gradually, was rewritten as well to bring a more coherent information section with all relevant information. The section should now be considerably easier to read, especially in the parts, which were causing confusion in the previous instructions. Aside from a large number of improvements, the section now also received a dedicated troubleshooting subsection and numerous new information. The section can be found under [https://wiki.pine64.org/wiki/PinePhone\_Pro#Software](https://wiki.pine64.org/wiki/PinePhone_Pro#Software). As it is often asked where bugs can be reported and how projects can be supported, new articles regarding [where to report bugs](https://wiki.pine64.org/wiki/Where_to_Report_Bugs) and [how to contribute to projects](https://wiki.pine64.org/wiki/How_to_Contribute) were started as well, which will be gradually improved and extended over time. In this context it can be noted that all community projects are happy about any form of contribution. Knowledge of coding is not required, instead there are various ways to contribute to projects, for example with designs, ideas, translations, documentation, through hardware or with creative work, or by simply being a positive member of the community. On this note, I want to thank everyone for their unremitting help. Without your contributions, the community would simply not be what it is today.
+The software section of the PinePhone Pro article, which was extended gradually, was rewritten as well to bring a more coherent information section with all relevant information. The section should now be considerably easier to read, especially in the parts, which were causing confusion in the previous instructions. Aside from a large number of improvements, the section now also received a dedicated troubleshooting subsection and numerous new information. The section can be found under [https://wiki.pine64.org/wiki/PinePhone\_Pro#Software](https://wiki.pine64.org/wiki/PinePhone_Pro#Software). As it is often asked where bugs can be reported and how projects can be supported, new articles regarding [where to report bugs](/documentation/Introduction/Where_to_report_bugs) and [how to contribute to projects](/documentation/Introduction/How_to_Contribute) were started as well, which will be gradually improved and extended over time. In this context it can be noted that all community projects are happy about any form of contribution. Knowledge of coding is not required, instead there are various ways to contribute to projects, for example with designs, ideas, translations, documentation, through hardware or with creative work, or by simply being a positive member of the community. On this note, I want to thank everyone for their unremitting help. Without your contributions, the community would simply not be what it is today.
 
 There is one more noteworthy piece of information concerning documentation of mobile Linux software: [LinuxPhoneApps.org](https://linuxphoneapps.org) finally quietly launched at the end of March. It [lists](https://linuxphoneapps.org/apps/) all the apps that were (and still are) listed on LINMOBapps. The list is presented in a way that is more friendly to PinePhone's Firefox browser, preventing it from asking whether it should kill the script that slows things down. The list now has more apps, with more being added slowly but steadily. Note that not all apps are packaged for your distribution nor are they all to be considered feature-complete. If you want to follow, join or help out the further development of the site, check out the [LinuxPhoneApps FAQ](https://linuxphoneapps.org/docs/help/faq/).
 

content/blog/december-update-a-year-in-review.md

@@ -90,7 +90,7 @@ N.B. Comments on the blog post need to be in English and follow our [Community R
 
 Thank you to everyone who contributed to the projects in 2021. I particularly want to thank our admins, [Matthew (Fire219)](https://twitter.com/fire219_SIMPL) and [Marek (Gamiee)](https://twitter.com/gamelaster), for their work. For those who don’t know, they are the people who put out the occasional fires and make sure that the cogs of the project keep turning. And a big shout-out to the moderators, who are doing a great job keeping our communication protocols clutter-free and safe. I also want to thank all of our partner projects - [Manjaro](https://manjaro.org/) and [KDE](https://kde.org/) in particular - for their work on our devices and their commitment to our shared community. I cannot forget about all the contributors, whom there are too many to mention individually, that make projects such as the PinePhone (Pro), the PineTime, and PineDio possible. Lastly, I want to thank all of you in the community for actively supporting us - I hope we did right by you yet another year. My best wishes to everyone - have a great holiday season. 
 
-This month’s [PineTalk](http://pine64.org/pinetalk/) will be recorded live on December 15th. Brian ([33YN2](https://mastodon.online/web/accounts/61817)) and Justin (Porky) will be using the ‘stage’ feature on [Discord](https://discord.gg/pine64), found at the bottom of the server’s channel list. I encourage you all to join in, ask questions and stick around afterwards for a chat with the hosts and other community members. In case you miss it, the episode will be available in an edited format a few days later on the podcast streaming platform of your choice, as per usual.
+This month’s [PineTalk](http://pine64.org/podcast/) will be recorded live on December 15th. Brian ([33YN2](https://mastodon.online/web/accounts/61817)) and Justin (Porky) will be using the ‘stage’ feature on [Discord](https://discord.gg/pine64), found at the bottom of the server’s channel list. I encourage you all to join in, ask questions and stick around afterwards for a chat with the hosts and other community members. In case you miss it, the episode will be available in an edited format a few days later on the podcast streaming platform of your choice, as per usual.
 
 ![](/blog/images/Malware-notification-Telegram.png) ![](/blog/images/Malware-notification-discord-1024x94.png)
 

content/blog/december-update-merry-christmas-and-happy-new-pinetab.md

@@ -156,13 +156,13 @@ For now our plans concern non-Pro devices, in part because no Pro-grade RISC-V c
 
 # PineTab2
 
-Before we get to discussing the new PineTab2 let me first explain what happened to its predecessor. The original PineTab was conceived alongside the PinePhone in early 2018 at a small pub in Brussels, and a little less than 2 years later the PinPhone and PineTab became available for order. At that time a global pandemic was something that could only be experienced through the medium of film. I think it is fair to say that none of us could have truly imagined what a global pandemic would entail for the entire world, let alone understood the consequences it would have for hardware production, electronics supply chains and global economics. There is no need for me to recap how the pandemic unfolded, what effect it had on production in mainland China or explain the hardships businesses had to endure as a consequence of this, but suffice to say that the original PineTab was a victim of COVID and its fallout. For those interested in the details, I encourage you to browse the blog’s [PineTab tag](https://www.pine64.org/tag/pinetab/)– I did my best to keep the community updated on the original device’s status throughout 2020-2021. In all fairness I should also make it clear that PineTab’s death was, in some part, a choice on our part as decisions were made to allocate resources to secure PinePhone’s availability throughout late 2020 and early 2021.
+Before we get to discussing the new PineTab2 let me first explain what happened to its predecessor. The original PineTab was conceived alongside the PinePhone in early 2018 at a small pub in Brussels, and a little less than 2 years later the PinPhone and PineTab became available for order. At that time a global pandemic was something that could only be experienced through the medium of film. I think it is fair to say that none of us could have truly imagined what a global pandemic would entail for the entire world, let alone understood the consequences it would have for hardware production, electronics supply chains and global economics. There is no need for me to recap how the pandemic unfolded, what effect it had on production in mainland China or explain the hardships businesses had to endure as a consequence of this, but suffice to say that the original PineTab was a victim of COVID and its fallout. For those interested in the details, I encourage you to browse the blog’s [PineTab tag](https://www.pine64.org/tags/pinetab/)– I did my best to keep the community updated on the original device’s status throughout 2020-2021. In all fairness I should also make it clear that PineTab’s death was, in some part, a choice on our part as decisions were made to allocate resources to secure PinePhone’s availability throughout late 2020 and early 2021.
 
 ![](/blog/images/pPineTab2-pcb-1024x768.jpg)
 
 **A look at PineTab2's PCB**
 
-By the time production of the PineTab became viable again we felt that the original design could and indeed should be improved on. By late 2021 there was also a great candidate SoC for a second generation PineTab – the RK3566. I have written extensively about the RK3566 in recent months in the [context of the Quartz64](https://www.pine64.org/category/quartz64/), but in a nutshell, it is a modern mid-range quad-core Cortex-A55 processor that integrates a Mali-G52 MP2 GPU and supports up-to 8GB of RAM. It is a dream-of-a-soc for small form-factor devices with space-constrained chassis since it runs cool, offers a wide variety of modern and fast IO, has a solid price-to-performance ratio and is genuinely future-proof. The one thing that the SoC didn’t have for a time was mature Linux support – but this is no longer the case (see _Newsflash_ section). Software development for the RK3566 platform is booming and Linux has now reached a high level of maturity with both mainline and BSP Linux supporting nearly all core functionality of the chipset. I feel it is fair to say that it is now a prime candidate for porting mobile OSes to.
+By the time production of the PineTab became viable again we felt that the original design could and indeed should be improved on. By late 2021 there was also a great candidate SoC for a second generation PineTab – the RK3566. I have written extensively about the RK3566 in recent months in the [context of the Quartz64](https://www.pine64.org/tags/quartz64/), but in a nutshell, it is a modern mid-range quad-core Cortex-A55 processor that integrates a Mali-G52 MP2 GPU and supports up-to 8GB of RAM. It is a dream-of-a-soc for small form-factor devices with space-constrained chassis since it runs cool, offers a wide variety of modern and fast IO, has a solid price-to-performance ratio and is genuinely future-proof. The one thing that the SoC didn’t have for a time was mature Linux support – but this is no longer the case (see _Newsflash_ section). Software development for the RK3566 platform is booming and Linux has now reached a high level of maturity with both mainline and BSP Linux supporting nearly all core functionality of the chipset. I feel it is fair to say that it is now a prime candidate for porting mobile OSes to.
 
 ![](/blog/images/PineTab2-case-back-off-1024x768.jpg)
 

content/blog/february-update-post-cny-and-fosdem-status-report.md

@@ -16,10 +16,10 @@ tags:
 cover: 
   image: "Header.jpg"
 images:
-  - "/blog/images/Header.jpg"
+  - "/blog/images/header_with_pinephone.jpg"
 ---
 
-![](/blog/images/Header.jpg)
+![](/blog/images/header_with_pinephone.jpg)
 
 **Nemo Mobile and Ubuntu Touch on the PinePhone at FOSDEM 2020**
 
@@ -68,7 +68,7 @@ As for the production and availability of the HardROCK64 and SOEdge AI module an
 
 There is plenty of good news, but let us start with the bad. The bad news is that we need to postpone the production of the RK3399 upgrade kit for the original Pinebook once again. Don’t worry, we’re not shelving it, we’re just prioritizing other things - such as the newly announced HardROCK64 and SOEdge - due to the limited manufacturing capacity (caused by the aforementioned pandemic in China). Having already postponed the release of the upgrade kit thrice now, I rather not promise something for a fourth time. Instead I’ll say: it's in the works, and as soon as I know something with a high degree of certainty I’ll make sure to let you all know. 
 
-On to better news. We now have a solution to the original NVMe adapter problems, where the adapter with an NVMe SSD would not fit properly in the laptop chassis. The solution was surprisingly simple, but required us to manufacture a custom holder for the SSD. I apologize for not keeping you up-to-date on the status of this solution; I didn’t post anything on the subject because I had no insight into the process. If you have the original NVMe adapter for the Pinebook Pro, please send an email to [[email protected]](https://www.pine64.org/[email protected]) with the following in the subject field: 
+On to better news. We now have a solution to the original NVMe adapter problems, where the adapter with an NVMe SSD would not fit properly in the laptop chassis. The solution was surprisingly simple, but required us to manufacture a custom holder for the SSD. I apologize for not keeping you up-to-date on the status of this solution; I didn’t post anything on the subject because I had no insight into the process. If you have the original NVMe adapter for the Pinebook Pro, please send an email to `[email protected]` with the following in the subject field: 
 
 **_Subject: New PBP NVMe adapter holder \[original order number\]_**
 

content/blog/february-update-show-and-tell.md

@@ -65,7 +65,7 @@ This may just be the most news-packed update since July last year, so strap in f
 
 ### Housekeeping
 
-I want to start by giving [Peter](https://twitter.com/linmobblog) and [Ezra](https://twitter.com/Elatronion) - our [PineTalk](https://www.pine64.org/pinetalk/) Podcast hosts - a huge shutout. They've worked really hard on the first two episodes of the podcast and, judging by the number of episode downloads, so far their style has resonated well with the community. In the last episode they spoke to [Dalton Durst](https://twitter.com/UnivrsalSuprBox) from UBports, discussed the recent announcement of [PinePhone Community Editions coming to a close](https://www.pine64.org/2021/02/02/the-end-of-community-editions/) and answered some questions from the community. PineTalk is now available on all major platforms, including Spotify and Apple's Podcast app, and I highly encourage you to subscribe to the [RSS feed](https://www.pine64.org/feed/mp3/). 
+I want to start by giving [Peter](https://twitter.com/linmobblog) and [Ezra](https://twitter.com/Elatronion) - our [PineTalk](https://www.pine64.org/podcast/) Podcast hosts - a huge shutout. They've worked really hard on the first two episodes of the podcast and, judging by the number of episode downloads, so far their style has resonated well with the community. In the last episode they spoke to [Dalton Durst](https://twitter.com/UnivrsalSuprBox) from UBports, discussed the recent announcement of [PinePhone Community Editions coming to a close](https://www.pine64.org/2021/02/02/the-end-of-community-editions/) and answered some questions from the community. PineTalk is now available on all major platforms, including Spotify and Apple's Podcast app, and I highly encourage you to subscribe to the [RSS feed](https://www.pine64.org/feed/mp3/). 
 
 ![](/blog/images/PineTalkPP-1024x768.jpg)