From d1dfa860812a7c692be9d1c12c5c2d20f0921622 Mon Sep 17 00:00:00 2001 From: Arksine Date: Mon, 1 Mar 2021 15:53:35 -0500 Subject: [PATCH] docs: fix typos in last web_api update Signed-off-by: Eric Callahan --- docs/web_api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/web_api.md b/docs/web_api.md index 8f393bd..5463e70 100644 --- a/docs/web_api.md +++ b/docs/web_api.md @@ -14,10 +14,10 @@ Moonraker's API registration along with the desire to keep consistency between mulitple API protocols results in an HTTP API that does not completely adhere to the standard. -Moonraker is capable of parsing request arguments from the body -(either json or form-data depending on the `Content-Type` header) and from +Moonraker is capable of parsing request arguments from the both the body +(either JSON or form-data depending on the `Content-Type` header) and from the query string. All arguments are grouped together in one data structure, -with body arguments taking precedence over query query arguments. Thus +with body arguments taking precedence over query arguments. Thus if the same argument is supplied both in the body and in the query string the body argument would be used. It is left up to the client developer to decide exactly how they want to provide arguments, however