Skip to content

Commit e2dd78c

Browse files
committed
Fix header level for new section
The Structural Interoperability section should be a subsection of the OpenAPI Description Structure section.
1 parent dd8c0aa commit e2dd78c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

versions/3.1.1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ An OpenAPI Description (OAD) MAY be made up of a single document or be divided i
140140

141141
It is RECOMMENDED that the entry OpenAPI document be named: `openapi.json` or `openapi.yaml`.
142142

143-
### <a name="structuralInteroperability"></a>Structural Interoperability
143+
#### <a name="structuralInteroperability"></a>Structural Interoperability
144144

145145
When parsing an OAD, JSON or YAML objects are parsed into specific Objects (such as [Operation Objects](#operationObject), [Response Objects](#responseObject), [Reference Objects](#referenceObject), etc.) based on the parsing context. Depending on how references are arranged, a given JSON or YAML object can be parsed in multiple different contexts:
146146

0 commit comments

Comments
 (0)