aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUMTS at Teleco <crt@teleco.ch>2026-02-15 16:08:33 +0100
committerUMTS at Teleco <crt@teleco.ch>2026-02-15 16:08:33 +0100
commitda4932c80b3d7209c1a6607cf632e35789be60b1 (patch)
tree0b02265890f8776ba1c57a1418a05da4b7d98929
parent2a024b48e41af8a85b53775ff463532d53ae6e7f (diff)
Typo
-rw-r--r--README.md2
-rw-r--r--overview.md2
2 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index b2eca14..c2b23c2 100644
--- a/README.md
+++ b/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)
diff --git a/overview.md b/overview.md
index 6b01e3e..3cb247c 100644
--- a/overview.md
+++ b/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.