Skip to content

Commit 26c934e

Browse files
authored
Merge pull request #4882 from ralfhandl/3.2-code-block-language-lowercase
3.2 code block language: convention is to use lowercase
2 parents 796eb84 + 912a96e commit 26c934e

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

src/oas.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -270,7 +270,7 @@ Unless specified otherwise, relative references are resolved using the URLs defi
270270

271271
Assume a retrieval URI of `https://device1.example.com` for the following OpenAPI Document:
272272

273-
```YAML
273+
```yaml
274274
openapi: 3.2.0
275275
$self: https://apidescriptions.example.com/foo
276276
info:
@@ -5353,7 +5353,7 @@ For OpenAPI Documents, this source is the OpenAPI Object's `$self` field, while
53535353

53545354
Assume the retrieval URI of the following document is `file://home/someone/src/api/openapi.yaml`:
53555355

5356-
```YAML
5356+
```yaml
53575357
openapi: 3.2.0
53585358
$self: https://example.com/api/openapi
53595359
info:
@@ -5368,7 +5368,7 @@ paths:
53685368

53695369
Assume the retrieval URI for the following document is `https://git.example.com/shared/blob/main/shared/foo.yaml`:
53705370

5371-
```YAML
5371+
```yaml
53725372
openapi: 3.2.0
53735373
$self: https://example.com/api/shared/foo
53745374
info:
@@ -5416,7 +5416,7 @@ Note that this is purely an example, and support for such multipart documents or
54165416

54175417
RFC2557 was written to allow sending hyperlinked sets of documents as email attachments, in which case there would not be a retrieval URI for the multipart attachment (although the format could also be used in HTTP as well).
54185418

5419-
```MULTIPART
5419+
```multipart
54205420
--boundary-example
54215421
Content-Type: application/openapi+yaml
54225422
Content-Location: https://example.com/api/openapi.yaml
@@ -5473,7 +5473,7 @@ If no base URI is provided from either of the previous sources, the next source
54735473

54745474
Assume this document was retrieved from `https://example.com/api/openapis.yaml`:
54755475

5476-
```YAML
5476+
```yaml
54775477
openapi: 3.2.0
54785478
info:
54795479
title: Example API
@@ -5489,7 +5489,7 @@ components:
54895489

54905490
Assume this document was retrieved from `https://example.com/api/schemas/foo`:
54915491

5492-
```JSON
5492+
```json
54935493
{
54945494
"type": "object",
54955495
"properties": {
@@ -5514,7 +5514,7 @@ Let's re-consider the first example in this appendix, but with relative URI-refe
55145514

55155515
Assume that the following is retrieved from `https://staging.example.com/api/openapi`:
55165516

5517-
```YAML
5517+
```yaml
55185518
openapi: 3.2.0
55195519
$self: /api/openapi
55205520
info:
@@ -5529,7 +5529,7 @@ paths:
55295529

55305530
Assume the retrieval URI for the following document is `https://staging.example.com/api/shared/foo`:
55315531

5532-
```YAML
5532+
```yaml
55335533
openapi: 3.2.0
55345534
$self: /api/shared/foo
55355535
info:

0 commit comments

Comments
 (0)