Sync with internal changes

Signed-off-by: Raphiel Rollerscaperers <[email protected]>

docs/getting-started/brand.mdx

@@ -4,15 +4,15 @@ sidebar_position: 2
 
 # Brand Guidelines
 
-The helluvaOS and hentaiOS name, the helluvaOS and hentaiOS logo, and are the property of The hentaiOS Project
+The helluvaOS and hentaiOS name, The helluvaOS and hentaiOS logo, The helluvaOS and hentaiOS marks, are the property of The hentaiOS Project.
 If you want to use these brands to indicate their association with your device or build, adhere to the guidelines on this page. All creatives that include or reference helluvaOS, hentaiOS, or The hentaiOS Project Trademarks usage must be reviewed and approved by the The hentaiOS Project brand team.
 
 ## hentaiOS and/or helluvaOS
 
-The use of hentaiOS and helluvaOS on a marketing materials related to the builds is restricted to [Compliant Devices](../technical-data/intro.md) only. The following are guidelines for the hentaiOS and/or helluvaOS brand and related assets that can be used for compliant devices.
+The use of hentaiOS and helluvaOS brand on a marketing materials related to the builds is restricted to [Compliant Devices](../technical-data/intro.md) only. The following are guidelines for the hentaiOS and/or helluvaOS brand and related assets that can be used for compliant devices.
 
 - The hentaiOS Project reserves the right to require hentaiOS, helluvaOS and/or The hentaiOS Project branding on compatible devices and any related materials, which includes but isn't limited to Changelogs, Release Posts, Boot-up Sequence, and Marketing Materials.
-- hentaiOS and/or helluvaOS should always be lowercased and is never plural or possesive.
+- hentaiOS and/or helluvaOS should always be lowercased in the index zero and is never plural or possesive.
 - hentaiOS and/or helluvaOS should be used only as a term to refer to the Operating System (OS) of your device. If you're unsure whether your use meets our guidelines, follow this simple test: If you can replace "hentaiOS/helluvaOS" with "The hentaiOS/helluvaOS Platform" and the text still makes sense, then you may use this term.
 
 ## hentaiOS and helluvaOS Logo

docs/technical-data/performance.md

@@ -16,7 +16,7 @@ Performance can fluctuate dramatically for high-performance long-running apps, e
 
 Maintainers:
 
-- [C-0-0] MUST NOT using Touch Boosting and instead, use libperf.
+- [C-0-0] MUST NOT using Touch Boosting and instead, use libperf and uclamp.
 - [C-0-1] MUST implement efficient frequency into libperf through Power Hints.
     We suggest that you avoid assigning CPU 0 and 1 to tasks other than TA (Top-App) as that it's generally utilizing CPU 0 and 1 extensively.
 - [C-0-2] MUST NOT overly boosting everything, because **Performance is not "all-about-boosting".** Efficiency is all that matters in this case, for getting efficient frequencies, you can use [freqbench](https://github.com/kdrag0n/freqbench).