fix typo in house-of-tangerine

Author: Kyle-Kyle

glibc_2.31/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {

glibc_2.32/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {

glibc_2.33/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {

glibc_2.34/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {

glibc_2.35/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {

glibc_2.36/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {

glibc_2.37/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {

glibc_2.38/house_of_tangerine.c

@@ -49,7 +49,7 @@
  *  *to make the PoC more reliable we need to malloc and probe the current top chunk size,
  *  this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead
  *
- * Special Thanks to pepsipu for creating the challenge "High Frequency Trading"
+ * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles"
  * from Pico CTF 2024 that inspired this exploitation technique
  */
 int main() {