chore(docs): update docs and references for OAS to 3.0.4 (#390)

* chore(docs): update examples and references to OAS 3.0.4

Author: frankkilcommins

src/components/Homepage.astro

@@ -43,7 +43,7 @@ const basePath = import.meta.env.BASE_URL;
       buttonTitle="View Docs"
       optionalText="View on GitHub"
       path={`${basePath}specification/v3_0/about/`}
-      optionalPath="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md"
+      optionalPath="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.4.md"
       cards={2}
       ><svg
         height="16"

src/content/docs/specification/v3_0/Authentication/api-keys.md

@@ -35,7 +35,7 @@ API keys are supposed to be a secret that only the client and server know. Like
 In OpenAPI 3.0, API keys are described as follows:
 
 ```yaml
-openapi: 3.0.0
+openapi: 3.0.4
 ---
 # 1) Define the key name and location
 components:

src/content/docs/specification/v3_0/Authentication/basic-authentication.md

@@ -21,7 +21,7 @@ Authorization: Basic ZGVtbzpwQDU1dzByZA==
 Using OpenAPI 3.0, you can describe Basic authentication as follows:
 
 ```yaml
-openapi: 3.0.0
+openapi: 3.0.4
 ---
 components:
   securitySchemes:

src/content/docs/specification/v3_0/Authentication/bearer-authentication.md

@@ -21,7 +21,7 @@ The Bearer authentication scheme was originally created as part of [OAuth 2.0](/
 In OpenAPI 3.0, Bearer authentication is a security scheme with `type: http` and `scheme: bearer`. You first need to define the security scheme under `components/securitySchemes`, then use the `security` keyword to apply this scheme to the desired scope – global (as in the example below) or specific operations:
 
 ```yaml
-openapi: 3.0.0
+openapi: 3.0.4
 ---
 # 1) Define the security scheme type (HTTP bearer)
 components:

src/content/docs/specification/v3_0/Authentication/cookie-authentication.md

@@ -34,7 +34,7 @@ Cookie: JSESSIONID=abcde12345
 In OpenAPI 3.0 terms, cookie authentication is an [API key](/docs/specification/authentication/api-keys/) that is sent `in: cookie`. For example, authentication via a cookie named `JSESSIONID` is defined as follows:
 
 ```yaml
-openapi: 3.0.0
+openapi: 3.0.4
 ---
 # 1) Define the cookie name
 components:

src/content/docs/specification/v3_0/Authentication/openid-connect-discovery.md

@@ -33,7 +33,7 @@ This URL returns a JSON listing of the OpenID/OAuth endpoints, supported scopes
 OpenAPI 3.0 lets you describe OpenID Connect Discovery as follows:
 
 ```yaml
-openapi: 3.0.0
+openapi: 3.0.4
 ---
 # 1) Define the security scheme type and attributes
 components:

src/content/docs/specification/v3_0/Data Models/data-models.md

@@ -8,7 +8,7 @@ sidebar:
 OAS **3** This guide is for OpenAPI 3.0.
 :::
 
-OpenAPI 3.0 data types are based on an extended subset [JSON Schema Specification Wright Draft 00](https://tools.ietf.org/html/draft-wright-json-schema-00#section-4.2) (aka Draft 5). The data types are described using a [Schema object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#schemaObject). To learn how to model various data types, see the following topics:
+OpenAPI 3.0 data types are based on an extended subset [JSON Schema Specification Wright Draft 00](https://tools.ietf.org/html/draft-wright-json-schema-00#section-4.2) (aka Draft 5). The data types are described using a [Schema object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.4.md#schema-object). To learn how to model various data types, see the following topics:
 
 - [Data Types](/docs/specification/data-models/data-types/)
 - [Enums](/docs/specification/data-models/enums/)

src/content/docs/specification/v3_0/Data Models/keywords.md

@@ -72,7 +72,7 @@ OpenAPI schemas can also use the following keywords that are not part of JSON Sc
 
 ### References
 
-[OpenAPI 3.0 – Schema Object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#schema-object)
+[OpenAPI 3.0 – Schema Object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.4.md#schema-object)
 
 [JSON Schema Validation](https://tools.ietf.org/html/draft-wright-json-schema-validation-00) – JSON Schema keyword reference
 

src/content/docs/specification/v3_0/Data Models/oneof-anyof-allof-not.md

@@ -156,8 +156,6 @@ The following request bodies are **not valid**:
   "age": 3        # Does not include the pet_type property
 }
 
-
-
 {
   "pet_type": "Cat",
   "bark": true    # The `Cat` schema does not have the `bark` property

src/content/docs/specification/v3_0/Data Models/representing-xml.md

@@ -274,7 +274,7 @@ Note that the `xml.name` property of the wrapping element (`books` in our exampl
 
 ### Reference
 
-[XML Object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#xmlObject)
+[XML Object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.4.md#xml-object)
 
 _Did not find what you were looking for? [Ask the community](https://community.smartbear.com/t5/Swagger-Open-Source-Tools/bd-p/SwaggerOSTools)  
 Found a mistake? [Let us know](https://github.com/swagger-api/swagger.io/issues)_