Fix typos and consistent naming for Llamactl across documentation

docs/advanced/backends.md

@@ -1,10 +1,10 @@
 # Backends
 
-LlamaCtl supports multiple backends for running large language models. This guide covers the available backends and their configuration.
+Llamactl supports multiple backends for running large language models. This guide covers the available backends and their configuration.
 
 ## Llama.cpp Backend
 
-The primary backend for LlamaCtl, providing robust support for GGUF models.
+The primary backend for Llamactl, providing robust support for GGUF models.
 
 ### Features
 
@@ -107,7 +107,7 @@ options:
 
 ## Future Backends
 
-LlamaCtl is designed to support multiple backends. Planned additions:
+Llamactl is designed to support multiple backends. Planned additions:
 
 ### vLLM Backend
 
@@ -137,7 +137,7 @@ Integration with Ollama for easy model management:
 
 ### Automatic Detection
 
-LlamaCtl can automatically detect the best backend:
+Llamactl can automatically detect the best backend:
 
 ```yaml
 backends:

docs/advanced/monitoring.md

@@ -1,10 +1,10 @@
 # Monitoring
 
-Comprehensive monitoring setup for LlamaCtl in production environments.
+Comprehensive monitoring setup for Llamactl in production environments.
 
 ## Overview
 
-Effective monitoring of LlamaCtl involves tracking:
+Effective monitoring of Llamactl involves tracking:
 
 - Instance health and performance
 - System resource usage
@@ -15,7 +15,7 @@ Effective monitoring of LlamaCtl involves tracking:
 
 ### Health Checks
 
-LlamaCtl provides built-in health monitoring:
+Llamactl provides built-in health monitoring:
 
 ```bash
 # Check overall system health
@@ -45,7 +45,7 @@ curl http://localhost:8080/metrics
 
 ### Configuration
 
-Add LlamaCtl as a Prometheus target:
+Add Llamactl as a Prometheus target:
 
 ```yaml
 # prometheus.yml
@@ -59,7 +59,7 @@ scrape_configs:
 
 ### Custom Metrics
 
-Enable additional metrics in LlamaCtl:
+Enable additional metrics in Llamactl:
 
 ```yaml
 # config.yaml
@@ -76,7 +76,7 @@ monitoring:
 
 ## Grafana Dashboards
 
-### LlamaCtl Dashboard
+### Llamactl Dashboard
 
 Import the official Grafana dashboard:
 
@@ -135,7 +135,7 @@ groups:
         labels:
           severity: critical
         annotations:
-          summary: "LlamaCtl instance {{ $labels.instance_name }} is down"
+          summary: "Llamactl instance {{ $labels.instance_name }} is down"
           
       - alert: HighMemoryUsage
         expr: llamactl_instance_memory_percent > 90
@@ -170,7 +170,7 @@ receivers:
     slack_configs:
       - api_url: 'https://hooks.slack.com/services/...'
         channel: '#alerts'
-        title: 'LlamaCtl Alert'
+        title: 'Llamactl Alert'
         text: '{{ range .Alerts }}{{ .Annotations.summary }}{{ end }}'
 ```
 
@@ -373,7 +373,7 @@ curl http://localhost:8080/metrics | grep rate_limit
 **Metrics not appearing:**
 1. Check Prometheus configuration
 2. Verify network connectivity
-3. Review LlamaCtl logs for errors
+3. Review Llamactl logs for errors
 
 **High memory usage:**
 1. Check for memory leaks in profiles

docs/advanced/troubleshooting.md

@@ -1,6 +1,6 @@
 # Troubleshooting
 
-Common issues and solutions for LlamaCtl deployment and operation.
+Common issues and solutions for Llamactl deployment and operation.
 
 ## Installation Issues
 
@@ -29,7 +29,7 @@ Common issues and solutions for LlamaCtl deployment and operation.
 
 ### Permission Denied
 
-**Problem:** Permission errors when starting LlamaCtl
+**Problem:** Permission errors when starting Llamactl
 
 **Solutions:**
 1. Check file permissions:
@@ -269,7 +269,7 @@ Common issues and solutions for LlamaCtl deployment and operation.
 
 ### High CPU Usage
 
-**Problem:** LlamaCtl consuming excessive CPU
+**Problem:** Llamactl consuming excessive CPU
 
 **Diagnostic Steps:**
 1. Identify CPU-intensive processes:
@@ -302,7 +302,7 @@ Common issues and solutions for LlamaCtl deployment and operation.
 
 ### Connection Refused
 
-**Problem:** Cannot connect to LlamaCtl web interface
+**Problem:** Cannot connect to Llamactl web interface
 
 **Diagnostic Steps:**
 1. Check if service is running: