Fix links in index and installation documentation for improved navigation

Author: nicosammito

docs/index.mdx

@@ -27,17 +27,17 @@ Before using any action from Centaurus, make sure you have:
 
 | Action | Description | Status |
 |--------|-------------|--------|
-| [GLS](./Actions/GLS/overview.md) | GLS ShipIT integration for creating and managing shipments | ✅ Available |
+| [GLS](Actions/GLS/overview.md) | GLS ShipIT integration for creating and managing shipments | ✅ Available |
 
 ---
 
 ## Quick Links
 
-- [Installation Guide](./Guides/installation.md) — How to deploy an action on your self-hosted instance
-- [GLS Action Overview](./Actions/GLS/overview.md) — Get started with the GLS shipping integration
-- [GLS Configuration](./Actions/GLS/configs.md) — API keys and configuration options
-- [GLS Functions](./Actions/GLS/functions.md) — All available functions and their parameters
-- [GLS Types](./Actions/GLS/types.md) — Data types used across the GLS action
-- [GLS Events](./Actions/GLS/events.md) — Events emitted by the GLS action
-- [Common Use Cases](./Actions/GLS/use-cases.md) — Example workflows using the GLS action
-- [Troubleshooting](./Actions/GLS/troubleshooting.md) — FAQ and community support
+- [Installation Guide](installation.md) — How to deploy an action on your self-hosted instance
+- [GLS Action Overview](Actions/GLS/overview.md) — Get started with the GLS shipping integration
+- [GLS Configuration](Actions/GLS/configs.md) — API keys and configuration options
+- [GLS Functions](Actions/GLS/functions.md) — All available functions and their parameters
+- [GLS Types](Actions/GLS/types.md) — Data types used across the GLS action
+- [GLS Events](Actions/GLS/events.md) — Events emitted by the GLS action
+- [Common Use Cases](Actions/GLS/use-cases.md) — Example workflows using the GLS action
+- [Troubleshooting](Actions/GLS/troubleshooting.md) — FAQ and community support

docs/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](GLS/configs.md))
+- 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](GLS/configs.md) page.
+For action-specific variables (e.g. GLS API credentials), see the [GLS Configuration](Actions/GLS/configs.md) page.
 
 ---
 
@@ -119,5 +119,5 @@ If the action fails to start or connect, check:
 - That `HERCULES_AUTH_TOKEN` is valid and not expired
 - That `HERCULES_AQUILA_URL` points to the correct host and port
 - That Docker has access to the internet (for pulling the base image)
-- The service-specific credentials are correct (see [Troubleshooting](GLS/troubleshooting.md))
+- The service-specific credentials are correct (see [Troubleshooting](Actions/GLS/troubleshooting.md))