You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/oas.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,10 +62,10 @@ In order to preserve the ability to round-trip between YAML and JSON formats, YA
62
62
The recommendation in previous versions of this specification to restrict YAML to its "JSON" [schema ruleset](https://yaml.org/spec/1.2/spec.html#id2803231) allowed for the inclusion of certain values that (despite the name) cannot be represented in JSON.
63
63
OAD authors SHOULD NOT rely on any such JSON-incompatible YAML values.
64
64
65
-
### Case-Sensitivity
65
+
### CaseSensitivity
66
66
67
67
As most field names and values in the OpenAPI Specification are case-sensitive, this document endeavors to call out any case-insensitive names and values.
68
-
However, the case-sensitivity of field names and values that map directly to HTTP concepts follow the case-sensitivity rules of HTTP, even if this document does not make a note of every concept.
68
+
However, the casesensitivity of field names and values that map directly to HTTP concepts follow the casesensitivity rules of HTTP, even if this document does not make a note of every concept.
0 commit comments