Fixed Typo's

Fixed some Typo's and adjusted text to make more sense

src/routes/Api/v1/References/help/+page.md

@@ -8,7 +8,7 @@ Get the link to the documentation.
 /v1/help
 ```
 
-### Response
+### Example Response
 *text/plain*
 ```
 Please refer to the wiki at https://wiki.jonasjones.dev/Api/

src/routes/Api/v1/References/ping/+page.md

@@ -8,7 +8,7 @@ Test the API connection.
 /v1/ping
 ```
 
-### Response
+### Example Response
 *text/plain*
 ```
 pong

src/routes/Api/v1/References/version/+page.md

@@ -8,7 +8,7 @@ Get the API version
 /v1/version
 ```
 
-### Response
+### Example Response
 *application/json*
 ```json
 ["0.0.1+alpha-build01"]

src/routes/McWebserver/4.Performance/+page.md

@@ -2,9 +2,9 @@
 ---
 McWebserver attempts to be as lightweight as possible.
 
-An experiment shows that this is clearly the case. Even when the server is getting DDOS'ed and the website might not be available due to the high demand of the DDOS, the server still runs perfectly fine.
+An experiment shows that this is clearly the case. Even when the server is getting DDOS'd and the website might not be available due to the high demand of the DDOS, the server still runs perfectly fine.
 
-The following gif shows a ddos script using 300 threads (300 simultaneous requests at a time) and the server's MSPT (Milliseconds per Tick) only rising my about 2ms while under the DDOS attack.
+The following gif shows a DDOS script using 300 threads (300 simultaneous requests at the same time) and the server's MSPT (Milliseconds per Tick) only rises by about 2ms while under the DDOS attack.
 
 Notice: This isn't a scientific test and I wouldn't claim that the server can withstand a real DDOS attack. The results only give an idea of the performance impact under elevated load and medium demand.