Skip to content

Commit d907454

Browse files
committed
markdown linting fixes
1 parent c72aff6 commit d907454

2 files changed

Lines changed: 10 additions & 9 deletions

File tree

agency/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,10 +50,10 @@ Path Params:
5050

5151
If `device_id` is specified, `GET` will return a single vehicle record, otherwise it will be a list of vehicle records with pagination details per the [JSON API](https://jsonapi.org/format/#fetching-pagination) spec:
5252

53-
```
53+
```json
5454
{
55-
"vehicles": [ ... ]
56-
"links": {
55+
"vehicles": [ ... ]
56+
"links": {
5757
"first": "https://...",
5858
"last": "https://...",
5959
"prev": "https://...",

general-information.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -161,11 +161,11 @@ Note that to handle out-of-order events, the validity of the prior-state shall n
161161
| any | `unknown` | `missing` | The vehicle is not at its last reported GPS location, or that location is wildly in error |
162162
| any | `unknown` | `out_of_comms` | The vehicle is unable to transmit its GPS location |
163163

164-
NOTES:
164+
NOTES:
165165

166166
Should we try to handle "unlicensed movements"?
167167

168-
What's the best way to return from `unknown`?
168+
What's the best way to return from `unknown`?
169169

170170
[Top][toc]
171171

@@ -197,9 +197,10 @@ Accept: application/vnd.mds+json;version=0.3
197197
```
198198

199199
> Since versioning was not available from the start, the following APIs provide a fallback version if the `Accept` header is not set as specified above:
200-
> - The `provider` API must respond as if version `0.2` was requested.
201-
> - The `agency` API must respond as if version `0.3` was requested.
202-
> - The `policy` API must respond as if version `0.4` was requested.
200+
>
201+
> * The `provider` API must respond as if version `0.2` was requested.
202+
> * The `agency` API must respond as if version `0.3` was requested.
203+
> * The `policy` API must respond as if version `0.4` was requested.
203204
204205
If an unsupported or invalid version is requested, the API must respond with a status of `406 Not Acceptable`. If this occurs, a client can explicitly negotiate available versions.
205206

@@ -224,4 +225,4 @@ The client can use the returned value verbatim as a version request in the `Acce
224225
[agency]: /agency/README.md
225226
[policy]: /policy/README.md
226227
[provider]: /provider/README.md
227-
[toc]: #table-of-contents
228+
[toc]: #table-of-contents

0 commit comments

Comments
 (0)