@spree/docs 0.1.0 → 0.1.2

package/dist/api-reference/store-api/errors.md

@@ -51,7 +51,7 @@ Validation errors include an additional `details` field with per-field error mes
 | `404` | Not Found | Resource doesn't exist or isn't accessible |
 | `409` | Conflict | Resource was modified by another request (concurrent update) |
 | `422` | Unprocessable Content | Validation failed, invalid state transition, payment error |
-| `429` | Too Many Requests | Rate limit exceeded (see [Rate Limiting](/api-reference/store-api/rate-limitting)) |
+| `429` | Too Many Requests | Rate limit exceeded (see [Rate Limiting](rate-limitting.md)) |
 
 ## Error Codes
 
@@ -128,7 +128,7 @@ Validation errors include an additional `details` field with per-field error mes
 | Code | Status | Description |
 |------|--------|-------------|
 | `order_already_updated` | 409 | Order was modified by another concurrent request. Retry with fresh data. |
-| `idempotency_key_reused` | 422 | Idempotency key was already used with different request parameters. See [Idempotency](/api-reference/store-api/idempotency). |
+| `idempotency_key_reused` | 422 | Idempotency key was already used with different request parameters. See [Idempotency](idempotency.md). |
 
 ### Other Errors
 

package/dist/api-reference/store-api/idempotency.md

@@ -119,7 +119,7 @@ await client.carts.items.create(cartId, {
 
 ## Relationship with Optimistic Locking
 
-The Store API also uses [optimistic locking](/api-reference/store-api/introduction) via the `state_lock_version` field on orders. These mechanisms complement each other:
+The Store API also uses [optimistic locking](introduction.md) via the `state_lock_version` field on orders. These mechanisms complement each other:
 
 | Mechanism | Prevents | Scope |
 |-----------|----------|-------|

package/dist/api-reference/store-api/localization.md

@@ -64,7 +64,7 @@ curl -G 'http://localhost:3000/api/v3/store/products' \
 
 ## Country and Markets
 
-The `X-Spree-Country` header resolves the customer's [market](/developer/core-concepts/markets), which influences default locale and currency. Markets allow you to configure different pricing, languages, and product availability per region.
+The `X-Spree-Country` header resolves the customer's [market](../../developer/core-concepts/markets.md), which influences default locale and currency. Markets allow you to configure different pricing, languages, and product availability per region.
 
 
 ```typescript SDK
@@ -85,7 +85,7 @@ When a market is resolved from the country:
 1. The market's default locale is used (unless overridden by `X-Spree-Locale`)
 2. The market's default currency is used (unless overridden by `X-Spree-Currency`)
 
-You can also resolve the market explicitly using the [Markets API](/developer/sdk/store/markets):
+You can also resolve the market explicitly using the [Markets API](../../developer/sdk/store/markets.md):
 
 
 ```typescript SDK
@@ -130,7 +130,7 @@ Each value is resolved in the following order:
 
 ## Translated Content
 
-When a locale is set, all translatable fields are returned in the requested language. This includes product names, descriptions, category names, and other content managed through [translations](/developer/core-concepts/translations).
+When a locale is set, all translatable fields are returned in the requested language. This includes product names, descriptions, category names, and other content managed through [translations](../../developer/core-concepts/translations.md).
 
 
 ```typescript SDK
@@ -194,7 +194,7 @@ curl 'http://localhost:3000/api/v3/store/products/spree-tote' \
 
 ## Discovering Available Options
 
-Use the dedicated endpoints to discover which markets, countries, locales, and currencies are available. These are derived from your store's [markets](/developer/core-concepts/markets) configuration.
+Use the dedicated endpoints to discover which markets, countries, locales, and currencies are available. These are derived from your store's [markets](../../developer/core-concepts/markets.md) configuration.
 
 ### Markets
 

package/dist/api-reference/store-api/metadata.md

@@ -6,7 +6,7 @@ description: "How to store and retrieve custom metadata on carts, orders, and li
 
 The Store API supports storing arbitrary key-value **metadata** on carts (orders) and line items. Metadata is useful for tracking custom information like gift messages, attribution data, or integration-specific fields.
 
-> **NOTE:** Metadata is different from [metafields](/developer/core-concepts/metafields). Metadata is simple JSON storage (untyped, no schema), while metafields are structured, typed, and schema-defined. Use metadata for integration data and internal tracking. Use metafields for customer-facing custom attributes.
+> **NOTE:** Metadata is different from [metafields](../../developer/core-concepts/metafields.md). Metadata is simple JSON storage (untyped, no schema), while metafields are structured, typed, and schema-defined. Use metadata for integration data and internal tracking. Use metafields for customer-facing custom attributes.
 
 ## Cart Metadata
 
@@ -157,4 +157,4 @@ Metadata is stored as a flat JSON object. You can use any keys and values:
 | **Best for** | Integration data, tracking, attribution | Product specs, custom fields, customer-facing data |
 | **API access** | Write via Store API, read via Admin API | Read/write via both APIs |
 
-For more details on metafields, see the [Metafields guide](/developer/core-concepts/metafields).
+For more details on metafields, see the [Metafields guide](../../developer/core-concepts/metafields.md).