Typo

README.md

@@ -1,6 +1,8 @@
 # JsonDerulo API Spec. v2.0
 [![JsonDerulo API Spec](https://git.teleco.ch/crt/jsonderulo-api-spec.git/plain/images/jayson-de-json.png)]
 
+> Swallalala
+
 ## What is this?
 - JsonDerulo Compliant Server Requirements
   - JsonDerulo (v2) shouldn't be viewed as something only implemented by one backend (even if it is sofar only implemented by one which serves as reference called SeckelAPI)

overview.md

@@ -8,7 +8,7 @@ The server listens on `http://<host>:<port>`. Port is configurable, no specific
 
 ## Content Type
 
-Everything is JSON (Derulo bahahahahah). Requests and always responses use `Content-Type: application/json`.
+Everything is JSON (Derulo bahahahahah). Requests and all responses use `Content-Type: application/json`.
 
 The only exception is when a toolkit endpoint uses `response_format: "passthrough"` for proxying file downloads or something none Jayson from an upstream service. In that case the response mimetype comes from whatever upstream decides to send back.