general maintenance

CONTRIBUTING.md

@@ -8,7 +8,15 @@ Links should generally point to the original website, unless the original source
 ### Formatting
 When formatting your submission, avoid cramming everything into a single paragraph. Separate the information into logical sections.  
 
-If necessary, you can use GitHub's Markdown Alerts to reduce the mental load. However, it's easy to overuse them and make the page extremely cluttered.  
+If necessary, you can use GitHub's Markdown Alerts to reduce the mental load. However, it's easy to overuse them and make the page extremely cluttered. 
+
+Avoid wrapping entire sentences in link blocks. Try to keep them short.
+
+```patch
+- ...and [Unisoc requires a bunch of extra steps to unlock for whatever reason][Unisoc Unlock]...
++ ...and Unisoc requires a bunch of [extra steps to unlock][Unisoc Unlock] for whatever reason...
+
+```
 
 The use of text formatting is not necessary and is generally used for "comedic" effect.
 
@@ -35,11 +43,39 @@ A company is considered "safe" if it follows the standard Android (or SOC) proce
 ### Brief History
 If the company allowed unlocking in the past, or had different unlocking methods, it may be useful to devote a paragraph to a historical review.
 
+### Guides
+
+Brand Pages on the Wall may provide their own unlock instructions, but the instructions should be separated into a separate file and fully describe the process. A troubleshooting section is encouraged.
+
+The generic unlock guide to base your own on can be found here: [generic-unlock.md](/misc/generic-unlock.md).
+
 ### Additional Info (Not related to unlocking)
 The main focus of this list is bootloader unlocking, but other related topics may also be mentioned. It's best to mention them in one sentence and link to a source, rather than explaining them at length.
 
 Related topics include, but are not limited to: rooting, custom operating systems, ADB.
 
+### Links
+
+Links to external resources should be formatted as Markdown reference links. Links to other pages on the Wall can be formatted using the regular `[Example](/brands/...)` syntax.
+
+```
+An [Example Link][example-link] in the middle.
+
+*** <- Bottom of the page.
+
+[example-link]:https:...
+```
+
+Or you can also do this:
+
+```
+An [Example Link] in the middle.
+
+*** <- Bottom of the page.
+
+[Example Link]:https:...
+```
+
 ### Images
 It's fine to use images in brand pages, but they should have descriptive alt text and be small. The smaller size can be achieved by converting your images to lossy `.webp`.
 

README.md

@@ -1,4 +1,4 @@
-![Bootloader Unlock: Wall of Shame](https://github.com/melontini/bootloader-unlock-wall-of-shame/assets/104443436/2b9dbf70-faf3-49ab-886b-d88f50c5dbe0)
+![Banner. A lock and a key on fire on the left and the text 'Bootloader Unlock: Wall of Shame' on the right.](/misc/banner/banner.jpg)
 
 Keeping track of companies that "care about your data 🥺"
 

brands/google/README.md

@@ -5,7 +5,7 @@
 
 Allows unlocking on almost any non-carrier locked device, but is also a pioneer in making rooting and custom ROMs painful with things like Safety Net and Play Integrity. With the latest feat being RCS messaging which requires DEVICE integrity to work. (To prevent "spam", of course)
 
-Google is also one of the few OEMs to support custom AVB keys.
+Google is also one of the few OEMs to support [custom AVB keys](/README.md#custom-avb-keys).
 
 ***
 Authored by [melontini](https://github.com/melontini).

brands/nothing/README.md

@@ -6,5 +6,7 @@
 Nothing Phones can be unlocked via fastboot without any codes. The only requirement is 
 to enable **OEM unlocking** in **Developer Options** settings page. This is the same procedure as on Google Pixel.
 
+It is reported that Nothing phones support [custom AVB keys](/README.md#custom-avb-keys).
+
 ***
 Authored by [konradmb](https://github.com/konradmb).

brands/umidigi/README.md

@@ -2,7 +2,7 @@
 
 * 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][Unisoc Unlock], and therefore I wouldn't consider them completely safe. 
+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][Unisoc Unlock] for whatever reason, and therefore I wouldn't consider them completely safe. 
 
 MediaTek devices can follow the [**🔓️ Generic Unlock Guide**](/misc/generic-unlock.md).