Fix broken links (#1787)

openapi/components/schemas/CheckoutForm.yaml

@@ -22,7 +22,7 @@ properties:
     type: array
     description: |-
       List of plans that are applied to a customer order by default.
-      Plans describe how the customer must pay for products. For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/tag/Plans/).
+      Plans describe how the customer must pay for products. For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/Plans/).
     minItems: 1
     items:
       $ref: ./CheckoutFormPlan.yaml

openapi/components/schemas/Product.yaml

@@ -8,7 +8,7 @@ description: |-
   If you set a tax category identifier, taxes are calculated at invoice generation.
   If the product is shippable, shipping costs are calculated at invoice generation.
   Pricing and variations are set within plans.
-  For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/tag/Plans/).
+  For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/Plans/).
 properties:
   id:
     type: string
@@ -44,7 +44,7 @@ properties:
     description: |-
       Product options such as color, size, and so forth.
       Product option values are defined in plans.
-      For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/tag/Plans/).
+      For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/Plans/).
     type: array
     items:
       type: string

openapi/components/schemas/StorefrontCheckoutForm.yaml

@@ -21,7 +21,7 @@ properties:
     type: array
     description: |-
       List of plans that are applied to a customer order by default.
-      Plans describe how the customer must pay for products. For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/tag/Plans/).
+      Plans describe how the customer must pay for products. For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/Plans/).
     minItems: 1
     items:
       $ref: ./CheckoutFormPlan.yaml

openapi/components/schemas/StorefrontProduct.yaml

@@ -8,7 +8,7 @@ description: |-
   If you set a tax category identifier, taxes are calculated at invoice generation.
   If the product is shippable, shipping costs are calculated at invoice generation.
   Pricing and variations are set within plans.
-  For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/tag/Plans/).
+  For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/Plans/).
 properties:
   id:
     type: string
@@ -43,7 +43,7 @@ properties:
     description: |-
       Product options such as color, size, and so forth.
       Product option values are defined in plans.
-      For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/tag/Plans/).
+      For more information, see [Plans](https://www.rebilly.com/docs/dev-docs/api/Plans/).
     type: array
     items:
       type: string

openapi/components/schemas/Tag.yaml

@@ -1,7 +1,7 @@
 type: object
 description: |-
   Use tags to organize and categorize customers or KYC documents based on keywords.
-  For more information, see [Tags](https://www.rebilly.com/docs/dev-docs/api/tag/Tags/).
+  For more information, see [Tags](https://www.rebilly.com/docs/dev-docs/api/Tags/).
 required:
   - name
   - type

openapi/openapi.yaml

@@ -344,7 +344,7 @@ tags:
         - `credit-file-proof`: Verifies that there is an existing credit file with two sources that match the customer's name, DOB, and address.
 
       Rebilly parses and analyzes the documents and accepts or rejects them according to a configurable scoring algorithm.
-      When all document types in a KYC request are accepted, the status is fulfilled, and the [KYC request fulfilled webhook](https://www.rebilly.com/docs/dev-docs/api/operation/kyc-request-fulfilled/) is sent.
+      When all document types in a KYC request are accepted, the status is fulfilled, and the [KYC request fulfilled webhook](https://www.rebilly.com/docs/dev-docs/api/KYC-documents/kyc-request-fulfilled/) is sent.
 
       ### Credit file proof
 
@@ -421,7 +421,7 @@ tags:
       We recommend using this with the FramePay library, which helps you integrate a form into this API resource and create payment tokens.
   - name: Plans
     description: |-
-      Use pricing plans to describe how the customer must pay for [products](https://www.rebilly.com/docs/dev-docs/api/tag/Products/).
+      Use pricing plans to describe how the customer must pay for [products](https://www.rebilly.com/docs/dev-docs/api/Products/).
 
       Rebilly provides the following plan types:
 
@@ -440,7 +440,7 @@ tags:
     description: |-
       Use products to describe the goods and services that your business sells.
       A product also describes sales items on invoices and receipts.
-      Product pricing is defined in [plans](https://www.rebilly.com/docs/dev-docs/api/tag/Plans/).
+      Product pricing is defined in [plans](https://www.rebilly.com/docs/dev-docs/api/Plans/).
       A product may have one or many plans.
 
       For information on the product resource, see [Product](https://www.rebilly.com/docs/dev-docs/concepts/#products).