diff --git a/brands/alcatel/README.md b/brands/alcatel/README.md
index 02a8b26..af1cf0e 100644
--- a/brands/alcatel/README.md
+++ b/brands/alcatel/README.md
@@ -4,7 +4,9 @@
There's nothing to say about Alcatel really. They have fastboot removed from most of their phones and have no official unlock method.
- A lot of their phones are MediaTek based so you can try [mtkclient](https://github.com/bkerler/mtkclient).
+ A lot of their phones are MediaTek based so you can try [mtkclient].
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[mtkclient]:/README.md#mediatek
\ No newline at end of file
diff --git a/brands/apple/README.md b/brands/apple/README.md
index 691c3ce..8b5225f 100644
--- a/brands/apple/README.md
+++ b/brands/apple/README.md
@@ -5,11 +5,17 @@
This one is probably expected. No iPhone, iPad, iPod Touch or Apple TV model has had an unlockable bootloader.
Depending on your device or SoC, there are BootROM (hardware based) and iBoot (software based) exploits you can use to run unsigned code on iOS devices, such as:
-[checkm8 for A5-A11](https://theapplewiki.com/wiki/Checkm8_Exploit);
-[limera1n for A4, iPod touch 3G, and iPhone 3GS](https://theapplewiki.com/wiki/Limera1n_Exploit);
-[24kpwn for certain iPod touch 2G's and iPhone 3GS's](https://theapplewiki.com/wiki/0x24000_Segment_Overflow);
-[steaks4uce for iPod touch 2G's](https://theapplewiki.com/wiki/Usb_control_msg(0xA1,_1)_Exploit) for BootROM exploits,
-and [DRA for all 32-bit devices running iOS 7.x.x](https://theapplewiki.com/wiki/De_Rebus_Antiquis) for iBoot exploits.
+- [checkm8] for A5-A11;
+- [limera1n] for A4, iPod touch 3G, and iPhone 3GS;
+- [24kpwn] for certain iPod touch 2G's and iPhone 3GS's;
+- [steaks4uce] for iPod touch 2G's for BootROM exploits,
+- [DRA] for all 32-bit devices running iOS 7.x.x for iBoot exploits.
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[checkm8]:https://theapplewiki.com/wiki/Checkm8_Exploit
+[limera1n]:https://theapplewiki.com/wiki/Limera1n_Exploit
+[24kpwn]:https://theapplewiki.com/wiki/0x24000_Segment_Overflow
+[steaks4uce]:https://theapplewiki.com/wiki/Usb_control_msg(0xA1,_1)_Exploit
+[DRA]:https://theapplewiki.com/wiki/De_Rebus_Antiquis
\ No newline at end of file
diff --git a/brands/asus/README.md b/brands/asus/README.md
index ffba7f9..a10fbd9 100644
--- a/brands/asus/README.md
+++ b/brands/asus/README.md
@@ -4,11 +4,14 @@
Asus originally allowed you to unlock your bootloader via their website, however in November 2023, the website went down "for maintanence", Asus claimed it would come back, but it never did.
-Someone eventually found a way to unlock the bootloader on the Zenfone 9, and Asus responded, not by finally bringing the site back, but by [patching the method and introducing anti-rollback](https://www.reddit.com/r/zenfone/comments/19f4ny3/asus_now_actively_sabotaging_attempts_to_unlock/).
+Someone eventually found a way to unlock the bootloader on the Zenfone 9, and Asus responded, not by finally bringing the site back, but by [patching the method and introducing anti-rollback][anti-rollback].
-Following Asus's false claims of a bootloader unlock eventually coming back, a UK customer sued Asus for a refund of their phone, [and Asus lost.](https://www.androidpolice.com/asus-removed-bootloader-unlock-from-phones/)
+Following Asus's false claims of a bootloader unlock eventually coming back, a UK customer sued Asus for a refund of their phone, [and Asus lost][lawsuit].
Asus is still claiming the unlock site will come back eventuallly, but considering how long it's been closed, the anti-rollback, and them losing a lawsuit over their unlockable bootloader claims, it's safe to say it'll probably never come back.
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[anti-rollback]:https://www.reddit.com/r/zenfone/comments/19f4ny3/asus_now_actively_sabotaging_attempts_to_unlock/
+[lawsuit]:https://www.androidpolice.com/asus-removed-bootloader-unlock-from-phones/
\ No newline at end of file
diff --git a/brands/fairphone/README.md b/brands/fairphone/README.md
index 3c1924b..6e06d72 100644
--- a/brands/fairphone/README.md
+++ b/brands/fairphone/README.md
@@ -4,11 +4,14 @@
No, wait, I have a point.
-All Fairphones after 2 require you to request a code from [this](https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone) website to enable OEM unlock. There is nothing stopping them from requiring an account and having device unlock limits in the future. This is "proceed with caution" after all.
+All Fairphones after 2 require you to request a code from [this][unlock-website] website to enable OEM unlock. There is nothing stopping them from requiring an account and having device unlock limits in the future. This is "proceed with caution" after all.
Not very fair in my opinion, but whatever fairs your phone.
-> They also [broke Verified Boot](https://forum.fairphone.com/t/bootloader-avb-keys-used-in-roms-for-fairphone-3-4/83448/4), lol
+> They also [broke Verified Boot][verified-boot], lol
***
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[unlock-website]:https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone
+[verified-boot]:https://forum.fairphone.com/t/bootloader-avb-keys-used-in-roms-for-fairphone-3-4/83448/4
\ No newline at end of file
diff --git a/brands/htc/README.md b/brands/htc/README.md
index 1eba45a..0b4f39f 100644
--- a/brands/htc/README.md
+++ b/brands/htc/README.md
@@ -2,12 +2,16 @@
- Verdict: **⛔ Avoid!**
-In the past, HTC allowed you to unlock your bootloader on their [developer website](https://www.htcdev.com/bootloader), but in June 2018 for whatever reason, HTC announced that any new phones would not have unlockable bootloaders, however their developer website would remain up for older devices.
+In the past, HTC allowed you to unlock your bootloader on their [developer website], but in June 2018 for whatever reason, HTC announced that any new phones would not have unlockable bootloaders, however their developer website would remain up for older devices.
> [!NOTE]
> As of September 2024, the website is still up and working (tested with an HTC Raider), however since HTC hasn't supported it in over 6 years, it may go down at any time, and even for these legacy devices, BS applies.
-HTC had a system known as "S-ON/S-OFF", with S-ON enabled, [the only partitions that can be flashed are system and recovery](https://www.htcdev.com/bootloader/about_unlock_process), all other partitions are read only. While HTC claims you can write boot with S-ON, it's complicated. For whatever reason, HTC made it so you can't flash boot.img from recovery, if you want to flash boot.img, you have to flash it in fastboot, meaning if you want to flash a ROM, you have to install it in recovery, then reboot to fastboot and flash boot.img, then you can boot. There have been systems to work around this, such as TWRP's [HTC Dumlock](https://xdaforums.com/t/htc-dumlock-flash-boot-from-recovery-without-fastboot-updated-2012-02-28-v2.1509743/). There are ways to achieve S-OFF, but it's different for each device. Search for your specific device on [XDA](https://xdaforums.com). Do note that due to the age of most of these tools, they may require legacy operating systems such as **Ubuntu 14.04 or Windows 7**.
+HTC had a system known as "S-ON/S-OFF", with S-ON enabled, [the only partitions that can be flashed are system and recovery][s-system], all other partitions are read only. While HTC claims you can write boot with S-ON, it's complicated. For whatever reason, HTC made it so you can't flash boot.img from recovery, if you want to flash boot.img, you have to flash it in fastboot, meaning if you want to flash a ROM, you have to install it in recovery, then reboot to fastboot and flash boot.img, then you can boot. There have been systems to work around this, such as TWRP's [HTC Dumlock]. There are ways to achieve S-OFF, but it's different for each device. Search for your specific device on [XDA](https://xdaforums.com). Do note that due to the age of most of these tools, they may require legacy operating systems such as **Ubuntu 14.04 or Windows 7**.
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[developer website]:https://www.htcdev.com/bootloader
+[s-system]:https://www.htcdev.com/bootloader/about_unlock_process
+[HTC Dumlock]:https://xdaforums.com/t/htc-dumlock-flash-boot-from-recovery-without-fastboot-updated-2012-02-28-v2.1509743/
\ No newline at end of file
diff --git a/brands/huawei/README.md b/brands/huawei/README.md
index c5178bc..60e8524 100644
--- a/brands/huawei/README.md
+++ b/brands/huawei/README.md
@@ -7,11 +7,15 @@
In the past, Huawei allowed you to unlock with a special code you get by submitting some information to emui.com (IMEI, serial, model, and product ID), but in 2018 "corporate values have changed" and the site went down.
Worse, on Android 10+, the unlock command has been **completely removed** from fastboot.
-Certain Kirin-based phones can use [PotatoNV](https://github.com/melontini/bootloader-unlock-wall-of-shame#kirin)
+Certain Kirin-based phones can use [PotatoNV]
Paid methods:
I don't recommend paid methods due to general sketchiness. I have used one of these tools a while ago, it was okay.
-Through HCU-client (Not everything is supported + incredible prices [hcu-client.com](https://hcu-client.com/buy/)) or DC-Unlocker (Same problems as HCU [dc-unlocker.com](https://www.dc-unlocker.com/buy))
+Through HCU-client (Not everything is supported + incredible prices [hcu-client.com]) or DC-Unlocker (Same problems as HCU [dc-unlocker.com])
***
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[PotatoNV]:/README.md#kirin
+[hcu-client.com]:https://hcu-client.com/buy/
+[dc-unlocker.com]:https://www.dc-unlocker.com/buy
\ No newline at end of file
diff --git a/brands/lg/README.md b/brands/lg/README.md
index be424f5..13e7bec 100644
--- a/brands/lg/README.md
+++ b/brands/lg/README.md
@@ -2,9 +2,12 @@
- Verdict: **⛔ Avoid!**
-In the past, LG had a developer portal which could be used to unlock phones on their website, however it only supported international models of their phones, but in December 2021, LG [announced](https://www.reddit.com/r/LineageOS/comments/r961u3/termination_of_lg_mobile_developer_website/) the developer portal would be shutting down due to LG ending production of all phones.
+In the past, LG had a developer portal which could be used to unlock phones on their website, however it only supported international models of their phones, but in December 2021, LG [announced][announcement-archive] the developer portal would be shutting down due to LG ending production of all phones.
-On some models (such as the Stylo 3 Plus and G6), the bootloader can still be unlocked via `fastboot oem unlock` **only if** [the phone is a T-Mobile model.](https://xdaforums.com/t/unlock-bootloader-tmo.3578099/)
+On some models (such as the Stylo 3 Plus and G6), the bootloader can still be unlocked via `fastboot oem unlock` **only if** [the phone is a T-Mobile model][t-mobile-unlock].
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[announcement-archive]:https://www.reddit.com/r/LineageOS/comments/r961u3/termination_of_lg_mobile_developer_website/
+[t-mobile-unlock]:https://xdaforums.com/t/unlock-bootloader-tmo.3578099/
\ No newline at end of file
diff --git a/brands/meizu/README.md b/brands/meizu/README.md
index 77e3bcc..f7491ac 100644
--- a/brands/meizu/README.md
+++ b/brands/meizu/README.md
@@ -3,7 +3,10 @@
- Verdict: **⛔ Avoid!**
There's not a lot to say about Meizu.
-They've never had unlockable bootloaders, and although there are a number of unofficial methods. Some Snapdragon devices have a [FRP exploit you can use in EDL to unlock](https://github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/FRP-Method), If your device is unsupported by the FRP exploit and isn't supported by mtkclient, there are [paid services](https://github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/Unlock-Bootloader) which you can use at your own risk.
+They've never had unlockable bootloaders, and although there are a number of unofficial methods. Some Snapdragon devices have a [FRP exploit you can use in EDL to unlock][fpr-exploit], If your device is unsupported by the FRP exploit and isn't supported by mtkclient, there are [paid services][paid-services] which you can use at your own risk.
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[fpr-exploit]:https://github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/FRP-Method
+[paid-services]:https://github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/Unlock-Bootloader
\ No newline at end of file
diff --git a/brands/microsoft/README.md b/brands/microsoft/README.md
index 73be035..67fc624 100644
--- a/brands/microsoft/README.md
+++ b/brands/microsoft/README.md
@@ -2,9 +2,12 @@
- Verdict: **⚠️ Proceed with caution!**
-While Microsoft doesn't provide an official unlocking method, an [unofficial method](https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/Install/UnlockingBootloader.md) has been available for their Android devices basically ever since Microsoft began making Android phones, and Microsoft hasn't bothered to patch it, and Windows is possible to run on an unlocked bootloader Surface Duo, so it seems like the bootloader will remain unlockable for now, but do note Microsoft can patch the unofficial method at any time.
+While Microsoft doesn't provide an official unlocking method, an [unofficial method][android-unlock] has been available for their Android devices basically ever since Microsoft began making Android phones, and Microsoft hasn't bothered to patch it, and Windows is possible to run on an unlocked bootloader Surface Duo, so it seems like the bootloader will remain unlockable for now, but do note Microsoft can patch the unofficial method at any time.
-As for Windows Phones, once again, no official methods, but an [unofficial method](http://allaboutwindowsphone.com/features/item/24245_Aguideforunlockingthebootloade.php) has been around for a while, and supports all Mirosoft-made Lumias except for the 540 and 535, as Windows Phone hasn't been supported since 2017, it is highly unlikely this is going to be patched.
+As for Windows Phones, once again, no official methods, but an [unofficial method][win-phone-unlock] has been around for a while, and supports all Mirosoft-made Lumias except for the 540 and 535, as Windows Phone hasn't been supported since 2017, it is highly unlikely this is going to be patched.
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[android-unlock]:https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/Install/UnlockingBootloader.md
+[win-phone-unlock]:http://allaboutwindowsphone.com/features/item/24245_Aguideforunlockingthebootloade.php
\ No newline at end of file
diff --git a/brands/motorola/README.md b/brands/motorola/README.md
index ed59d40..753f6de 100644
--- a/brands/motorola/README.md
+++ b/brands/motorola/README.md
@@ -2,18 +2,24 @@
- Verdict: **⚠️ Proceed with caution!**
-To start off, to unlock your bootloader you have to submit a request on their website, which is pretty bad on its own (*wink* Huawei). But how do you know if your device is unlockable? Well...
-
-* [This page](https://en-us.support.motorola.com/app/answers/detail/a_id/87215) says that "Most of our latest devices support our bootloader unlock program."
-* [This page](https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a) says only "Photon Q 4G LTE, DROID RAZR M(Developer Edition), DROID RAZR HD(Developer Edition CDMA-LTE), MOTOROLA RAZR HD (Rest of World -UMTS/LTE), MOTOROLA RAZR HD (Rogers Canada - UMTS/LTE) and MOTOROLA RAZR i are supported by the Bootloader Unlock site."
-* [And from this conversation](https://xdaforums.com/t/how-to-guide-unlocking-using-deeptest-gdpr.4585829/post-88734665) [turistu](https://github.com/turistu) had with their support: "most of our E devices doesn't support bootloader unlock program. Please see below a list of devices that support the bootloader unlock program : g100, g51 , g71 , g200 , g52 , g82 , g42 , g62 , g32"
-* There's also an unofficial way with CID to check if your device can be unlocked, check here: [xdaforums.com](https://xdaforums.com/t/guide-un-locking-motorola-bootloader.4079111/post-85375429)
-* Motorola also requires the phone to have a stable internet connection for at least a week for the bootloader to be unlocked, this is not mentioned anywhere on the unlock website but has been confirmed by [posts on the Motorola development forum](https://forums.lenovo.com/topic/findpost/15261/5289637/6254146)
+To start off, to unlock your bootloader you have to submit a request on their website, which is pretty bad on its own (*wink* [Huawei](/brands/huawei/README.md)). But how do you know if your device is unlockable? Well...
+* [This page][Most Devices] says that "Most of our latest devices support our bootloader unlock program."
+* [This page][Some Devices] says only "Photon Q 4G LTE, DROID RAZR M(Developer Edition), DROID RAZR HD(Developer Edition CDMA-LTE), MOTOROLA RAZR HD (Rest of World -UMTS/LTE), MOTOROLA RAZR HD (Rogers Canada - UMTS/LTE) and MOTOROLA RAZR i are supported by the Bootloader Unlock site."
+* [And from this conversation][turistu's post] [turistu](https://github.com/turistu) had with their support: "most of our E devices doesn't support bootloader unlock program. Please see below a list of devices that support the bootloader unlock program : g100, g51 , g71 , g200 , g52 , g82 , g42 , g62 , g32"
+* There's also an unofficial way with CID to check if your device can be unlocked, check here: [xdaforums.com][CID check]
> Moto used confusion! It seems pretty effective...
+Motorola also requires the phone to have a stable internet connection for at least a week for the bootloader to be unlocked, this is not mentioned anywhere on the unlock website but has been confirmed by [posts on the Motorola development forum][Connection Required].
+
***
Additional info provided by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
CID info provided by [FPSensor](https://github.com/FPSensor).
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[Most Devices]:https://en-us.support.motorola.com/app/answers/detail/a_id/87215
+[Some Devices]:https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a
+[turistu's post]:https://xdaforums.com/t/how-to-guide-unlocking-using-deeptest-gdpr.4585829/post-88734665
+[CID check]:https://xdaforums.com/t/guide-un-locking-motorola-bootloader.4079111/post-85375429
+[Connection Required]:https://forums.lenovo.com/topic/findpost/15261/5289637/6254146
\ No newline at end of file
diff --git a/brands/nokia/README.md b/brands/nokia/README.md
index 1b83501..95c6947 100644
--- a/brands/nokia/README.md
+++ b/brands/nokia/README.md
@@ -5,15 +5,19 @@
In the flaming pile of HMD's "great" decisions to improve Nokia, one stands out more than others: They decided to follow the fresh "lock the bootloader" trend.
Why was this necessary? I don't know...
-Well, anyway. Models released before early 2019 can request unlocking using Hikari Calyx's unofficial service [hikaricalyx.com](https://hikaricalyx.com/request-bootloader-unlock)
+Well, anyway. Models released before early 2019 can request unlocking using Hikari Calyx's unofficial service [hikaricalyx.com][hikari-service]
-And for some other models, Hikari Calyx has a repo with prototype ABLs. [fih-firmware.hikaricalyx.com](https://fih-firmware.hikaricalyx.com/protoabl/)
+And for some other models, Hikari Calyx has a repo with prototype ABLs. [fih-firmware.hikaricalyx.com][hikari-abl]
Models 7.2, 8.3 and 5.3 can be unlocked offline, while others may require HMD Device Kit **which is not public and requires a service account.**
-As for Windows Phones, most models have an [unofficial method](http://allaboutwindowsphone.com/features/item/24245_Aguideforunlockingthebootloade.php) of unlocking, which is supported by most Nokia Lumias, except for the 620, 720, and 1320.
+As for Windows Phones, most models have an [unofficial method][lumia-unlock] of unlocking, which is supported by most Nokia Lumias, except for the 620, 720, and 1320.
***
Windows Phone info by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
Updated info provided by [Hikari Calyx](https://github.com/HikariCalyx).
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[hikari-service]:https://hikaricalyx.com/request-bootloader-unlock
+[hikari-abl]:https://fih-firmware.hikaricalyx.com/protoabl/
+[lumia-unlock]:http://allaboutwindowsphone.com/features/item/24245_Aguideforunlockingthebootloade.php
\ No newline at end of file
diff --git a/brands/oppo/README.md b/brands/oppo/README.md
index d931f27..d66ef40 100644
--- a/brands/oppo/README.md
+++ b/brands/oppo/README.md
@@ -7,12 +7,16 @@ The most annoying thing about them is that you *can* unlock your bootloader, but
As per Realme, they decided that segregating people by ~~race~~ their phone's region is cool. If you didn't buy your phone in China or India, chances are you won't be unlocking anything anytime soon.
-In April-May 2023 you could unlock any Realme phone using this script [rmx3474-rooting](https://github.com/turistu/rmx3474-rooting), but on May 26th Realme posted this joke of an announcement on their forum [c.realme.com](https://c.realme.com/in/post-details/1671137365285982208). (They've deleted the original announcement)
+In April-May 2023 you could unlock any Realme phone using this script [rmx3474-rooting], but on May 26th Realme posted this joke of an announcement on their forum [c.realme.com][announcement]. (They've deleted the original announcement)
Since then, they have forced their servers to only return "new struct" keys, which have model data attached, making the script useless.
-In theory, if available, you could use full-OTA packages to change your phone's firmware region and use the deep testing app directly, but I can't verify that this works (please, correct me if I'm wrong). Guide: [xdaforums.com](https://xdaforums.com/t/change-region-via-full-ota.4535659/)
+In theory, if available, you could use full-OTA packages to change your phone's firmware region and use the deep testing app directly, but I can't verify that this works (please, correct me if I'm wrong). Guide: [xdaforums.com][Full-OTA region switch]
As for China and India... Seeing how easily Realme dropped the ball on their global users, I personally would be worried about their future plans. For now, you'll have to find and follow device-specific instructions at [c.realme.com](https://c.realme.com/in/). The process is pretty much the same for most phones, but newer models may require a HeyTap account.
***
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[rmx3474-rooting]:https://github.com/turistu/rmx3474-rooting
+[announcement]:https://c.realme.com/in/post-details/1671137365285982208
+[Full-OTA region switch]:https://xdaforums.com/t/change-region-via-full-ota.4535659/
\ No newline at end of file
diff --git a/brands/samsung/README.md b/brands/samsung/README.md
index 4401c19..423e88a 100644
--- a/brands/samsung/README.md
+++ b/brands/samsung/README.md
@@ -2,17 +2,22 @@
- Verdict: **⛔ Avoid!**
-If you have a North American device, well, uh... If you're lucky enough not to update for a while, you can check out [this paid service](https://xdaforums.com/t/android-unsamlock-bootloader-unlock-for-samsung-us-canada-devices.4215101/). (At your own risk)
+If you have a North American device, well, uh... If you're lucky enough not to update for a while, you can check out [this paid service][Paid North American Unlock]. (At your own risk)
If you bought your phone elsewhere, and it's not carrier locked, you can use the standard process, but brace yourself for all the breakage coming your way!
For example, unlocking will permanently trip Knox. As a result, *any* Knox-based features will be broken *even if you re-lock*. This includes, but not limited to: Samsung Pay, Pass, Flow, Health, Secure Folder, Secure Wi-Fi, Smart View. Can you be denied warranty? Probably...
-Some of those features can be fixed with this LsPosed module [KnoxPatch](https://github.com/BlackMesa123/KnoxPatch) and this Magisk Module [KnoxPatch#knoxpatch-enhancer](https://github.com/BlackMesa123/KnoxPatch#knoxpatch-enhancer).
+Some of those features can be fixed with this LsPosed module [KnoxPatch] and this Magisk Module [KnoxPatch#knoxpatch-enhancer].
-In addition, some basic features can, and will probably break, such as VoLTE, (thanks to Samsung's proprietary implementation) and in certain cases [even the camera](https://xdaforums.com/t/a52s-5g-sm-a528b-unlock-bootloader-camera-failed.4336007/).
+In addition, some basic features can, and will probably break, such as VoLTE, (thanks to Samsung's proprietary implementation) and in certain cases [even the camera][Unlock Breaks Camera].
> Info kindly provided by [aries-ts-indo](https://github.com/aries-ts-indo)!
***
Additional info provided by [aries-ts-indo](https://github.com/aries-ts-indo).
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[Paid North American Unlock]:https://xdaforums.com/t/android-unsamlock-bootloader-unlock-for-samsung-us-canada-devices.4215101/
+[KnoxPatch]:https://github.com/BlackMesa123/KnoxPatch
+[KnoxPatch#knoxpatch-enhancer]:https://github.com/BlackMesa123/KnoxPatch#knoxpatch-enhancer
+[Unlock Breaks Camera]:https://xdaforums.com/t/a52s-5g-sm-a528b-unlock-bootloader-camera-failed.4336007/
\ No newline at end of file
diff --git a/brands/sony/README.md b/brands/sony/README.md
index 9d8b046..168eaa9 100644
--- a/brands/sony/README.md
+++ b/brands/sony/README.md
@@ -3,11 +3,15 @@
- Verdict: **⚠️ Proceed with caution!**
Sony has an open policy for software developers:
-- They are releasing AOSP sources under [Sony Open Devices Program](https://developer.sony.com/open-source/aosp-on-xperia-open-devices).
-- Jolla provides first-class support for installing [Sailfish OS](https://shop.jolla.com/) on select Xperias. That wouldn't be possible without Sony's openness.
+- They are releasing AOSP sources under [Sony Open Devices Program].
+- Jolla provides first-class support for installing [Sailfish OS] on select Xperias. That wouldn't be possible without Sony's openness.
Since Sony likes to ruin a perfect thing:
-- Sony requires you to request an unlock code from [their servers](https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader). They can pull the plug anytime. You have to send your IMEI and agree to warranty voiding.
+- Sony requires you to request an unlock code from [their servers][Unlock Service]. They can pull the plug anytime. You have to send your IMEI and agree to warranty voiding.
***
-Authored by [konradmb](https://github.com/konradmb).
\ No newline at end of file
+Authored by [konradmb](https://github.com/konradmb).
+
+[Sony Open Devices Program]:https://developer.sony.com/open-source/aosp-on-xperia-open-devices
+[Sailfish OS]:https://shop.jolla.com/
+[Unlock Service]:https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader
\ No newline at end of file
diff --git a/brands/umidigi/README.md b/brands/umidigi/README.md
index 991a5c1..2db66bd 100644
--- a/brands/umidigi/README.md
+++ b/brands/umidigi/README.md
@@ -2,7 +2,9 @@
* Verdict **ℹ️ "Safe for now" :trollface:**
-Umidigi phones are generally unlockable, however due to them being a budget-focused manufacturer, they use Unisoc SoCs, and [Unisoc requires a bunch of extra steps to unlock for whatever reason](https://www.hovatek.com/forum/thread-32287.html), and therefore I wouldn't consider them completely safe. MediaTek Umidigi devies can just use flashing unlock/oem unlock in fastboot.
+Umidigi phones are generally unlockable, however due to them being a budget-focused manufacturer, they use Unisoc SoCs, and [Unisoc requires a bunch of extra steps to unlock for whatever reason][Unisoc Unlock], and therefore I wouldn't consider them completely safe. MediaTek Umidigi devies can just use flashing unlock/oem unlock in fastboot.
***
-Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
\ No newline at end of file
+Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
+
+[Unisoc Unlock]:https://www.hovatek.com/forum/thread-32287.html
\ No newline at end of file
diff --git a/brands/vivo/README.md b/brands/vivo/README.md
index c71ec4f..3f6e546 100644
--- a/brands/vivo/README.md
+++ b/brands/vivo/README.md
@@ -4,14 +4,18 @@
The BBK* family has an unlocking problem. If in case of OPPO/Realme they at least offer an app in some regions, Vivo is locked completely.
-Well, that is, if [xdaforums.com](https://xdaforums.com/t/how-to-unlock-bootloader-of-vivo-phones.3686690/) doesn't apply to you.
+Well, that is, if [xdaforums.com][BBK Fastboot] doesn't apply to you.
On pre-May 2022 firmware. I believe these methods *were* ~universal, but proceed with caution:
-* Vivo x70 Pro+: [xdaforums.com](https://xdaforums.com/t/vivo-x70-pro-bootloader-unlock-how-to-guide.4444989/)
-* Vivo Y31 2021: [xdaforums.com](https://xdaforums.com/t/unlocking-bootloader-rebooting-in-edl-without-testpoint-vivo-y31-2021.4440801/)
+* Vivo x70 Pro+: [xdaforums.com][Vivo x70 Pro+]
+* Vivo Y31 2021: [xdaforums.com][Vivo x70 Pro+]
\* BBK Electronics was deregistered as a company on 7 April 2023.
***
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[BBK Fastboot]:https://xdaforums.com/t/how-to-unlock-bootloader-of-vivo-phones.3686690/
+[Vivo x70 Pro+]:https://xdaforums.com/t/vivo-x70-pro-bootloader-unlock-how-to-guide.4444989/
+[Vivo Y31 2021]:https://xdaforums.com/t/unlocking-bootloader-rebooting-in-edl-without-testpoint-vivo-y31-2021.4440801/
\ No newline at end of file
diff --git a/brands/xiaomi/README.md b/brands/xiaomi/README.md
index a5541d7..c45501f 100644
--- a/brands/xiaomi/README.md
+++ b/brands/xiaomi/README.md
@@ -19,16 +19,20 @@ Additional BS applies:
- You will not receive OTA updates.
- your warranty will be void.
-Also, check out [Xiaomi-HyperOS-BootLoader-Bypass](https://github.com/MlgmXyysd/Xiaomi-HyperOS-BootLoader-Bypass) by [MlgmXyysd](https://github.com/MlgmXyysd).
+Also, check out [Xiaomi-HyperOS-BootLoader-Bypass] by [MlgmXyysd](https://github.com/MlgmXyysd).
> [!NOTE]
-> While not as extreme, if [xiaomiui.net](https://xiaomiui.net/how-unlock-bootloader-xiaomi-hyperos-53493/) is to be believed, global unlock has also undergone some changes:
+> While not as extreme, if [xiaomiui.net][global-requirements] is to be believed, global unlock has also undergone some changes:
> * Your Mi Account has been active for more than 30 days.
> * Xiaomi Community App version 5.3.31 or above.
> * You can only unlock the bootloader of 3 devices per year with your account.
-Look here if you want to learn about how Ximi's bootloader works: [Xiaomi-bootloader](https://github.com/lrh2000/Xiaomi-bootloader)
+Look here if you want to learn about how Ximi's bootloader works: [Xiaomi-bootloader]
***
Updated info provided by [n1ses](https://github.com/n1ses).
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[Xiaomi-HyperOS-BootLoader-Bypass]:https://github.com/MlgmXyysd/Xiaomi-HyperOS-BootLoader-Bypass
+[global-requirements]:https://xiaomiui.net/how-unlock-bootloader-xiaomi-hyperos-53493/
+[Xiaomi-bootloader]:https://github.com/lrh2000/Xiaomi-bootloader
\ No newline at end of file
diff --git a/brands/zte/README.md b/brands/zte/README.md
index 21f16cf..893af5f 100644
--- a/brands/zte/README.md
+++ b/brands/zte/README.md
@@ -5,7 +5,9 @@
- Verdict: **⛔ Avoid!**
Old devices (pre Android 8):
-[xdaforums.com](https://xdaforums.com/t/bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/)
+[xdaforums.com][pre-android-8]
***
-Authored by [melontini](https://github.com/melontini).
\ No newline at end of file
+Authored by [melontini](https://github.com/melontini).
+
+[pre-android-8]:https://xdaforums.com/t/bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/
\ No newline at end of file