From 193316bac60980431618418b64a196d18858885b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Javi=20Mart=C3=ADn?= Date: Sat, 8 Aug 2020 19:22:45 +0200 Subject: [PATCH] Apply spaces inside code span elements mdl rule --- doc/api/api_en.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api/api_en.md b/doc/api/api_en.md index cde087ce2..afe17a519 100644 --- a/doc/api/api_en.md +++ b/doc/api/api_en.md @@ -260,7 +260,7 @@ To retrieve the next page, you have to pass as a parameter the cursor received i ### Accessing several resources in a single request -This query requests information about several models in a single request: `Proposal`,` User`, `Geozone` and` Comment`: +This query requests information about several models in a single request: `Proposal`, `User`, `Geozone` and `Comment`: ``` { @@ -337,7 +337,7 @@ The response will look something like this: ### Example of too complex query -The main risk factor is when multiple collections of resources are requested in the same query. The maximum number of collections that can appear in the same query is limited to 2. The following query requests information from the `users`,` debates` and `proposals` collections, so it will be rejected: +The main risk factor is when multiple collections of resources are requested in the same query. The maximum number of collections that can appear in the same query is limited to 2. The following query requests information from the `users`, `debates` and `proposals` collections, so it will be rejected: ``` { @@ -382,7 +382,7 @@ The response will look something like this: } ``` -However, it is possible to request information belonging to more than two models in a single query, as long as you do not try to access the entire collection. For example, the following query that accesses the `User`,` Proposal` and `Geozone` models is valid: +However, it is possible to request information belonging to more than two models in a single query, as long as you do not try to access the entire collection. For example, the following query that accesses the `User`, `Proposal` and `Geozone` models is valid: ``` {