docs: enhance README formatting and clarity

README.md

@@ -30,10 +30,10 @@ Some side notes:
 4. For removable eSIM chip vendors: to have your chip supported by official builds of EasyEUICC when inserted,
    include the ARA-M hash `2A2FA878BC7C3354C2CF82935A5945A3EDAE4AFA`.
 
-[sgp.22]: https://www.gsma.com/solutions-and-impact/technologies/esim/gsma_resources/sgp-22-v2-2-2/
-[usb-ccid]: https://en.wikipedia.org/wiki/CCID_%28protocol%29
-[releases]: https://gitea.angry.im/PeterCxy/OpenEUICC/releases
-[actions]: https://gitea.angry.im/PeterCxy/OpenEUICC/actions
+[sgp.22]: https://www.gsma.com/solutions-and-impact/technologies/esim/gsma_resources/sgp-22-v2-2-2/ "SGP.22 v2.2.2"
+[usb-ccid]: https://en.wikipedia.org/wiki/CCID_%28protocol%29 "USB CCID Protocol"
+[releases]: https://gitea.angry.im/PeterCxy/OpenEUICC/releases "EasyEUICC Releases"
+[actions]: https://gitea.angry.im/PeterCxy/OpenEUICC/actions "OpenEUICC Actions"
 
 **This project is Free Software licensed under GNU GPL v3, WITHOUT the "or later" clause.**
 Any modification and derivative work **MUST** be released under the SAME license, which means, at the very least, that the source code **MUST** be available upon request.
@@ -85,7 +85,7 @@ There are two ways to include OpenEUICC in your AOSP-based system image:
    - No official `Android.bp` is provided for this case but it should be straightforward to write.
    - You might want to include [`privapp_whitelist_im.angry.openeuicc.xml`] as well.
 
-[`privapp_whitelist_im.angry.openeuicc.xml`]: privapp_whitelist_im.angry.openeuicc.xml
+[`privapp_whitelist_im.angry.openeuicc.xml`]: privapp_whitelist_im.angry.openeuicc.xml "OpenEUICC Privapp Whitelist"
 
 # FAQs