diff --git a/backend/proxy/proxy.cpp b/backend/proxy/proxy.cpp
index 728d4a8..5cf77df 100644
--- a/backend/proxy/proxy.cpp
+++ b/backend/proxy/proxy.cpp
@@ -1,4 +1,5 @@
-/* Copyright (c) 2007 Arash Partow (http://www.partow.net)
+/* 
+   Copyright (c) 2007 Arash Partow (http://www.partow.net)
    URL: http://www.partow.net/programming/tcpproxy/index.html
    Modified and adapted by Pwnzer0tt1
 */
diff --git a/docs/FiregexBenchmark.png b/docs/FiregexBenchmark.png
index 4f9a050..062d808 100644
Binary files a/docs/FiregexBenchmark.png and b/docs/FiregexBenchmark.png differ
diff --git a/tests/README.md b/tests/README.md
index b28c90f..06e8cfa 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -52,4 +52,7 @@ Benchmarks let you evaluate the performance of the proxy. You can run one by typ
 It uses iperf3 to benchmark the throughput in MB/s of the server, both with proxy, without proxy, and for each new added regex. It will automatically add a new random regex untill it has reached NUM_OF_REGEX specified in the arguments. 
 
 You will find a new benchmark.csv file containg the results.
+
+# Firegex Performance Results
+The test was performed on AMD Ryzen 7 3700X (16 thread) @ 3.600GHz, RAM Speed: 3200 MT/s (Dual Channel), kernel: 5.18.5-arch1-1
 ![Firegex Benchmark](/docs/FiregexBenchmark.png)