Merge pull request #5286 from notEthan/oas-appendix-f-uri

fix Appedix F URI inconsistencies (v3.3)

Author: ralfhandl

src/oas.md

@@ -5336,7 +5336,7 @@ components:
       content:
         application/json:
           schema:
-            $ref: "#/components/api/schemas/Foo"
+            $ref: "#/components/schemas/Foo"
   schemas:
     Foo:
       properties:
@@ -5457,7 +5457,7 @@ components:
 ```
 
 In this example, all of the `$self` and `$id` values are relative URI references consisting of an absolute path.
-This allows the retrieval URI to set the host (and scheme), in this case `https://staging.example.com`, resulting in the first document's `$self` being `https://staging.example.com/openapi`, and the second document's `$self` being `https://staging.example.com/api/shared/foo`, with `$id` values of `https://staging.example.com/api/schemas/foo` and `https://staging.example.com/api/schemas/bar`.
+This allows the retrieval URI to set the host (and scheme), in this case `https://staging.example.com`, resulting in the first document's `$self` being `https://staging.example.com/api/openapi`, and the second document's `$self` being `https://staging.example.com/api/shared/foo`, with `$id` values of `https://staging.example.com/api/schemas/foo` and `https://staging.example.com/api/schemas/bar`.
 Relative `$self` and `$id` values of this sort  allow the same set of documents to work when deployed to other hosts, e.g. `https://example.com` (production) or `https://localhost:8080` (local development).
 
 ## Appendix G: Parsing and Resolution Guidance