Fix URL encoding for Obtainium redirect links in blog and homepage features

Author: stesee

blog/2024-09-02-welcome/index.md

@@ -5,7 +5,7 @@ authors: [stesee]
 tags: [google play store, android, obtainium]
 ---
 
-**Update 2025 - rereleased: [![Obtainium](https://img.shields.io/badge/Obtainium-LockPDFy-green?style=flat&logo=android)](obtainium/redirect.html?r=obtainium://add/https://github.com/stesee/PDFEncrypt)**
+**Update 2025 - rereleased: [![Obtainium](https://img.shields.io/badge/Obtainium-LockPDFy-green?style=flat&logo=android)](obtainium/redirect.html?r=obtainium%3A%2F%2Fadd%2Fhttps%3A%2F%2Fgithub.com%2Fstesee%2FPDFEncrypt)**
 
 Google Play Store is a great platform to distribute Android apps. However, the recurring effort to keep the changing regulatory requirement up to date is not worth it for me. I have decided to let my dev profile fade away and focus on other things.
 

src/components/HomepageFeatures/index.tsx

@@ -31,7 +31,7 @@ const FeatureList: FeatureItem[] = [
         Encrypt and decrypt PDFs using LockPDFy. On premise and open source. <a href="https://www.microsoft.com/store/productId/9NC5KPZM2ZRM">
           <img src="https://img.shields.io/badge/Windows%20Store-LockPDFy-green?style=flat&logo=windows" alt="Windows Store" />
         </a>
-        <a href="obtainium/redirect.html?r=obtainium://add/https://github.com/stesee/PDFEncrypt">
+        <a href="obtainium/redirect.html?r=obtainium%3A%2F%2Fadd%2Fhttps%3A%2F%2Fgithub.com%2Fstesee%2FPDFEncrypt">
           <img src="https://img.shields.io/badge/Obtainium-LockPDFy-green?style=flat&logo=android" alt="Obtainium" />
         </a>
         <a href="blog/Bye%20bye%20google%20play%20store">