docs: fix hosting folder links to include correct path

Author: einari

Documentation/clients/dotnet/connection-strings.md

@@ -309,7 +309,7 @@ var options = new ChronicleOptions
 };
 ```
 
-See the [TLS Configuration](../../tls-configuration.md) documentation for more details on certificate setup.
+See the [TLS Configuration](../../tls-hosting/configuration.md) documentation for more details on certificate setup.
 
 ## Best Practices
 
@@ -378,6 +378,6 @@ If you encounter TLS errors:
 
 ## See Also
 
-- [TLS Configuration](../../tls-configuration.md)
+- [TLS Configuration](../../tls-hosting/configuration.md)
 - [Namespaces](namespaces.md)
 - [Getting Started](../../get-started/index.md)

Documentation/hosting/encryption-certificate.md

@@ -192,7 +192,7 @@ Ensure you have configured the certificate path and password as described above.
 
 ## Next Steps
 
-- [Local Certificates](local-certificates.md) - TLS certificate setup for development
-- [Production Hosting](production.md) - Production deployment requirements
-- [Configuration](configuration.md) - Complete configuration reference
+- [Local Certificates](hosting/local-certificates.md) - TLS certificate setup for development
+- [Production Hosting](hosting/production.md) - Production deployment requirements
+- [Configuration](hosting/configuration.md) - Complete configuration reference
 

Documentation/hosting/index.md

@@ -4,9 +4,9 @@ Chronicle provides multiple deployment options to suit different environments an
 
 ## Deployment Options
 
-- **[Production](production.md)** - Docker-based production deployment with MongoDB
-- **[Configuration](configuration.md)** - Complete configuration reference
-- **[Local Certificates](local-certificates.md)** - Generate and configure TLS certificates for local development
+- **[Production](hosting/production.md)** - Docker-based production deployment with MongoDB
+- **[Configuration](hosting/configuration.md)** - Complete configuration reference
+- **[Local Certificates](hosting/local-certificates.md)** - Generate and configure TLS certificates for local development
 - **Development** - Local development setup with MongoDB
 - **Docker Compose** - Multi-container setup for development and testing
 
@@ -17,7 +17,7 @@ All Chronicle hosting environments require:
 - **.NET 9 Runtime** - Chronicle is built on .NET 9
 - **MongoDB** - Primary storage backend for events and projections
 - **Network Access** - Chronicle exposes multiple ports for different services
-- **Configuration** - See [Configuration](configuration.md) for details
+- **Configuration** - See [Configuration](hosting/configuration.md) for details
 
 ## Architecture Overview
 

Documentation/hosting/local-certificates.md

@@ -246,5 +246,5 @@ If the client cannot connect:
 
 ## Next Steps
 
-- [Production Hosting](production.md) - Learn about production certificate requirements
-- [Configuration](configuration.md) - Complete configuration reference
+- [Production Hosting](hosting/production.md) - Learn about production certificate requirements
+- [Configuration](hosting/configuration.md) - Complete configuration reference

Documentation/hosting/production.md

@@ -18,7 +18,7 @@ docker pull cratis/chronicle:1.0.0
 
 ## Configuration
 
-Chronicle requires configuration to define its runtime behavior. For complete configuration details, see the [Configuration](configuration.md) guide.
+Chronicle requires configuration to define its runtime behavior. For complete configuration details, see the [Configuration](hosting/configuration.md) guide.
 
 The configuration file must be mounted into the container at `/app/chronicle.json`, or you can use environment variables with the `Cratis__Chronicle__` prefix.
 
@@ -80,11 +80,11 @@ volumes:
 1. **Use specific version tags** instead of `latest` for production deployments
 2. **Mount configuration as read-only** (`-v /path/to/chronicle.json:/app/chronicle.json:ro`)
 3. **Use environment-specific connection strings** for MongoDB
-4. **Configure appropriate timeouts** based on your infrastructure (see [Configuration](configuration.md))
+4. **Configure appropriate timeouts** based on your infrastructure (see [Configuration](hosting/configuration.md))
 5. **Enable health checks** for container orchestration
 6. **Set up monitoring** for all exposed ports
 7. **Use secrets management** for sensitive configuration values
-8. **Enable TLS** with proper certificates (see [TLS Configuration](../tls-configuration.md))
+8. **Enable TLS** with proper certificates (see [TLS Configuration](../tls-hosting/configuration.md))
 
 ## Health Checks
 
@@ -95,7 +95,7 @@ HEALTHCHECK --interval=30s --timeout=10s --start-period=30s --retries=3 \
   CMD curl -f http://localhost:8080/health || exit 1
 ```
 
-> **Note**: The health check endpoint path is configurable. See [Configuration](configuration.md#health-check-endpoint) for details.
+> **Note**: The health check endpoint path is configurable. See [Configuration](hosting/configuration.md#health-check-endpoint) for details.
 
 ## Security Considerations
 
@@ -104,7 +104,7 @@ HEALTHCHECK --interval=30s --timeout=10s --start-period=30s --retries=3 \
 - **Access Control**: Implement proper firewall rules for exposed ports
 - **Secrets Management**: Use external secret management for sensitive configuration
 - **Regular Updates**: Keep Chronicle and MongoDB images updated
-- **TLS Certificates**: Configure valid TLS certificates for production (see [TLS Configuration](../tls-configuration.md))
+- **TLS Certificates**: Configure valid TLS certificates for production (see [TLS Configuration](../tls-hosting/configuration.md))
 
 ## Scaling
 

Documentation/tls-configuration.md

@@ -78,7 +78,7 @@ var options = new ChronicleOptions
 };
 ```
 
-You can also enable TLS for development to test TLS-related functionality. See [Local Certificate Setup](local-certificates.md) for guidance on generating and configuring development certificates.
+You can also enable TLS for development to test TLS-related functionality. See [Local Certificate Setup](hosting/local-certificates.md) for guidance on generating and configuring development certificates.
 
 ### Production
 
@@ -117,8 +117,8 @@ For production environments, obtain certificates from:
 
 For development environments, generate self-signed certificates:
 
-- Using the [.NET CLI](local-certificates.md#option-1-using-net-cli-recommended-for-net-developers)
-- Using [OpenSSL](local-certificates.md#option-2-using-openssl)
+- Using the [.NET CLI](hosting/local-certificates.md#option-1-using-net-cli-recommended-for-net-developers)
+- Using [OpenSSL](hosting/local-certificates.md#option-2-using-openssl)
 
 ## Connection String Configuration
 
@@ -216,7 +216,7 @@ For development, use a Debug build which allows running without a certificate.
 
 ## See Also
 
-- [Local Certificate Setup](local-certificates.md) - Generate and configure development certificates
-- [Production Hosting](production.md) - Production deployment guidance
-- [Configuration](configuration.md) - Complete configuration reference
+- [Local Certificate Setup](hosting/local-certificates.md) - Generate and configure development certificates
+- [Production Hosting](hosting/production.md) - Production deployment guidance
+- [Configuration](hosting/configuration.md) - Complete configuration reference