Fix doc links

Author: Knerio

docs/Actions/GLS/configs.md

@@ -107,4 +107,4 @@ The value must be a valid `GLS_SHIPPER` object:
 }
 ```
 
-See [Types — GLS_SHIPPER](../types/#GLS_SHIPPER) for the full field reference.
+See [Types — GLS_SHIPPER](../GLS/types.md/#GLS_SHIPPER) for the full field reference.

docs/Actions/GLS/functions.md

@@ -56,7 +56,7 @@ createAddress(
 | `MobilePhonenumber` | string (min 4, max 35) | No | Mobile phone number |
 | `eMail` | string (max 80) | No | Email address |
 
-**Returns:** [`GLS_ADDRESS`](../types#GLS_ADDRESS)
+**Returns:** [`GLS_ADDRESS`](../GLS/types.md#GLS_ADDRESS)
 
 ---
 
@@ -83,7 +83,7 @@ createConsignee(
 | `Address` | GLS_ADDRESS | **Yes** | The delivery address for this consignee |
 | `Category` | `"BUSINESS"` \| `"PRIVATE"` | **Yes** | Whether the consignee is a business or private recipient |
 
-**Returns:** [`GLS_CONSIGNEE`](../types#GLS_CONSIGNEE)
+**Returns:** [`GLS_CONSIGNEE`](../GLS/types.md#GLS_CONSIGNEE)
 
 ---
 
@@ -114,7 +114,7 @@ createShipmentUnit(
 | `note2` | string (max 50) | No | Additional note printed on the label (line 2) |
 | `shipmentUnitService` | GLS_UNIT_SERVICE | No | Unit-level services (Cash, AddonLiability, HazardousGoods, etc.) |
 
-**Returns:** [`GLS_SHIPMENT_UNIT`](../types#GLS_SHIPMENT_UNIT)
+**Returns:** [`GLS_SHIPMENT_UNIT`](../GLS/types.md#GLS_SHIPMENT_UNIT)
 
 ---
 
@@ -140,7 +140,7 @@ createPrintingOptions(returnLabels: RETURN_LABELS): GLS_PRINTING_OPTIONS
 | `TemplateSet` | `NONE`, `D_200`, `PF_4_I`, `ZPL_200`, `ZPL_300`, ... | Label template set |
 | `LabelFormat` | `PDF`, `ZEBRA`, `INTERMEC`, `DATAMAX`, `TOSHIBA`, `PNG` | Output format |
 
-**Returns:** [`GLS_PRINTING_OPTIONS`](../types#GLS_PRINTING_OPTIONS)
+**Returns:** [`GLS_PRINTING_OPTIONS`](../GLS/types.md#GLS_PRINTING_OPTIONS)
 
 ---
 
@@ -169,7 +169,7 @@ createCustomContent(
 | `barcodeType` | `"EAN_128"` \| `"CODE_39"` | No | Barcode symbology |
 | `barcode` | string | No | Custom barcode value |
 
-**Returns:** [`GLS_CUSTOM_CONTENT`](../types#GLS_CUSTOM_CONTENT)
+**Returns:** [`GLS_CUSTOM_CONTENT`](../GLS/types.md#GLS_CUSTOM_CONTENT)
 
 ---
 
@@ -536,7 +536,7 @@ validateShipment
       └── validationResult.Issues[]
 ```
 
-See [Types — GLS_VALIDATE_SHIPMENT_REQUEST_DATA](../types#GLS_VALIDATE_SHIPMENT_REQUEST_DATA) for the input format.
+See [Types — GLS_VALIDATE_SHIPMENT_REQUEST_DATA](../GLS/types.md#GLS_VALIDATE_SHIPMENT_REQUEST_DATA) for the input format.
 
 ---
 

docs/Actions/GLS/overview.md

@@ -87,10 +87,10 @@ GLS_CREATE_PARCELS_RESPONSE  ← tracking IDs, barcode data, print data, routing
 
 ## Next steps
 
-- [Quick Start](../quick-start) — Create your first shipment in a few steps
-- [Configuration](../configs) — Full list of configuration options and how to get credentials
-- [Functions](../functions) — All available functions with parameter details
-- [Types](../types) — All data types used in the GLS Action
-- [Events](../events) — Events emitted by the GLS Action
-- [Common Use Cases](../use-cases) — Example flows for real-world scenarios
-- [Troubleshooting](../troubleshooting) — FAQ and community support
+- [Quick Start](../GLS/quick-start.md) — Create your first shipment in a few steps
+- [Configuration](../GLS/configs.md) — Full list of configuration options and how to get credentials
+- [Functions](../GLS/functions.md) — All available functions with parameter details
+- [Types](../GLS/types.md) — All data types used in the GLS Action
+- [Events](../GLS/events.md) — Events emitted by the GLS Action
+- [Common Use Cases](../GLS/use-cases.md) — Example flows for real-world scenarios
+- [Troubleshooting](../GLS/troubleshooting.md) — FAQ and community support

docs/Actions/GLS/quick-start.md

@@ -11,7 +11,7 @@ This guide walks you through creating your first GLS shipment using the GLS Acti
 
 ## Step 1: Install and configure the action
 
-Follow the [Installation Guide](../../Guides/installation) to deploy the GLS Action, then set the following configuration values in your Hercules admin panel (or `.env` file):
+Follow the [Installation Guide](../../Guides/installation.md) to deploy the GLS Action, then set the following configuration values in your Hercules admin panel (or `.env` file):
 
 | Config | Value |
 |--------|-------|
@@ -20,7 +20,7 @@ Follow the [Installation Guide](../../Guides/installation) to deploy the GLS Act
 | `ship_it_api_url` | GLS ShipIT endpoint (default: `https://api.gls-group.net/shipit-farm/v1/backend/rs`) |
 | `auth_url` | GLS auth endpoint (default: `https://api.gls-group.net/oauth2/v2/token`) |
 
-See [Configuration](./configs) for the full list of options and how to obtain credentials.
+See [Configuration](./configs.md) for the full list of options and how to obtain credentials.
 
 ---
 
@@ -128,7 +128,7 @@ The `GLS_CREATE_PARCELS_RESPONSE` contains everything you need:
 
 ## Common next steps
 
-- [Validate before creating](./functions#validateShipment) — Call `validateShipment` first to catch errors before committing
-- [Cancel a shipment](./functions#cancelShipment) — Use `cancelShipment` with the `TrackID` if something changes
-- [Reprint a label](./functions#reprintParcel) — Use `reprintParcel` if a label is lost or damaged
-- [Common Use Cases](./use-cases) — End-to-end examples for real-world scenarios
+- [Validate before creating](./functions.md#validateShipment) — Call `validateShipment` first to catch errors before committing
+- [Cancel a shipment](./functions.md#cancelShipment) — Use `cancelShipment` with the `TrackID` if something changes
+- [Reprint a label](./functions.md#reprintParcel) — Use `reprintParcel` if a label is lost or damaged
+- [Common Use Cases](./use-cases.md) — End-to-end examples for real-world scenarios

docs/Actions/GLS/troubleshooting.md

@@ -30,7 +30,7 @@ A: The action supports all major GLS shipment types and services, including:
 - Tyre service, addressee-only delivery
 - Saturday and next-working-day delivery (EXPRESS only)
 
-See [Functions](../functions.md) for the complete list.
+See [Functions](../GLS/functions.md) for the complete list.
 
 ---
 
@@ -73,7 +73,7 @@ A: Saturday delivery (and next-working-day delivery) requires the shipment's `Pr
 
 **Q: I get `ERROR_CREATING_GLS_SHIPMENT` — how do I find out what went wrong?**
 
-A: Use `validateShipment` first to check your shipment data before creating it. The validation response includes specific `Issues` with `Rule` and `Location` fields pointing to the problematic field. See [Use Cases — Validate before creating](./use-cases#use-case-2-validate-before-creating).
+A: Use `validateShipment` first to check your shipment data before creating it. The validation response includes specific `Issues` with `Rule` and `Location` fields pointing to the problematic field. See [Use Cases — Validate before creating](../GLS/use-cases.md#use-case-2-validate-before-creating).
 
 ---
 

docs/Actions/GLS/use-cases.md

@@ -297,7 +297,7 @@ Response:
       "ShippingDate": "2025-01-15",
       "Product": "PARCEL",
       "Consignee": {
-        "Address": { "Name1": "Jane Smith", "City": "Hamburg", ... }
+        "Address": { "Name1": "Jane Smith", "City": "Hamburg" } // ... and other parameters
       },
       "ShipmentUnit": [
         { "TrackID": "12345678", "Weight": "1.2", "ParcelNumber": "00123456789" }

docs/Guides/installation.md

@@ -20,7 +20,7 @@ Before you begin, make sure you have the following:
 - **Docker** and **Docker Compose** installed
 - A running **Aquila** server (part of the Hercules platform)
 - Your `HERCULES_AUTH_TOKEN` from the Aquila admin panel
-- Service-specific credentials (e.g. GLS API keys — see [GLS Configuration](../Actions/GLS/configs))
+- Service-specific credentials (e.g. GLS API keys — see [GLS Configuration](../Actions/GLS/configs.md))
 
 ---
 
@@ -71,7 +71,7 @@ HERCULES_ACTION_ID=gls-action
 HERCULES_SDK_VERSION=1.0.0
 ```
 
-For action-specific variables (e.g. GLS API credentials), see the [GLS Configuration](../Actions/GLS/configs) page.
+For action-specific variables (e.g. GLS API credentials), see the [GLS Configuration](../Actions/GLS/configs.md) page.
 
 ---