From c11668cd4eed364256a6ed46b150d393794a6d3b Mon Sep 17 00:00:00 2001 From: Ralf Handl Date: Sat, 7 Sep 2024 18:41:17 +0200 Subject: [PATCH] Update versions/3.0.4.md --- versions/3.0.4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/3.0.4.md b/versions/3.0.4.md index 086de31642..8bffc966e6 100644 --- a/versions/3.0.4.md +++ b/versions/3.0.4.md @@ -122,7 +122,7 @@ In order to preserve the ability to round-trip between YAML and JSON formats, YA An OpenAPI Description (OAD) MAY be made up of a single document or be divided into multiple, connected parts at the discretion of the author. In the latter case, [Reference Object](#reference-object) and [Path Item Object](#path-item-object) `$ref` keywords, as well as the [Link Object](#link-object) `operationRef` keyword, are used. Any document consisting entirely of an [OpenAPI Object](#openapi-object) is known as a **syntactically complete OpenAPI document**. -An OpenAPI document that does ***not*** reference any other documents is known as a **self-contained OpenAPI document.*** +An OpenAPI document that does _not_ reference any other documents is known as a **self-contained OpenAPI document**. A single-document description is therefore _both_ syntactically complete _and_ self-contained. In a multi-document description, the document containing the OpenAPI Object where parsing begins for a specific API's description is known as that API's **entry OpenAPI document**, or simply **entry document**.