diff --git a/MokoConsulting/monitor-mcp/Sites-Monitoring.-.-.md b/MokoConsulting/monitor-mcp/Sites-Monitoring.-.-.md
index 39a7a20..8ed85bb 100644
--- a/MokoConsulting/monitor-mcp/Sites-Monitoring.-.-.md
+++ b/MokoConsulting/monitor-mcp/Sites-Monitoring.-.-.md
@@ -2,7 +2,7 @@
 
 # Sites Monitoring
 
-The monitor MCP integrates with `sites.json` to manage monitored Joomla and Dolibarr sites. This provides a single source of truth for all client endpoints, driving Prometheus blackbox probes, Joomla API metrics, and Grafana dashboards.
+The monitor MCP integrates with `sites.json` to manage monitored MokoWaaS (Joomla) and MokoCRM (Dolibarr) sites. This provides a single source of truth for all client endpoints, driving Prometheus blackbox probes, Joomla API metrics, and Grafana dashboards.
 
 ## How it works
 
@@ -18,7 +18,7 @@ The monitor MCP integrates with `sites.json` to manage monitored Joomla and Doli
                               ├── blackbox-http.json  → Prometheus
                               ├── blackbox-ssl.json   → Prometheus
                               ├── joomla-monitor.conf → cron script
-                              └── Grafana dashboards  → one per client
+                              └── Grafana dashboards  → MokoWaaS / MokoCRM
 ```
 
 ## sites.json format
@@ -28,14 +28,14 @@ The monitor MCP integrates with `sites.json` to manage monitored Joomla and Doli
     "grafana": {
         "baseUrl": "https://bench.mokoconsulting.tech",
         "apiKey": "glsa_...",
-        "dashboardFolder": "Clients",
-        "dashboardFolderUid": "cfldz4r88nhfkc"
+        "dashboardFolder": "Endpoints",
+        "dashboardFolderUid": "..."
     },
     "sites": [
         {
             "name": "clientname-live",
             "url": "https://example.com",
-            "type": "joomla",
+            "type": "mokowaas",
             "client": "ClientName",
             "joomlaToken": "sha256:...",
             "akeebaSecret": "",
@@ -49,20 +49,22 @@ The monitor MCP integrates with `sites.json` to manage monitored Joomla and Doli
 
 | Type | Probes | API Monitoring |
 |------|--------|----------------|
-| `joomla` | HTTP, SSL | Version, updates, extensions, backup (via Joomla API) |
-| `dolibarr` | HTTP, SSL | Planned |
-| `gitea` | HTTP, SSL | -- |
-| `grafana` | HTTP, SSL | -- |
-| `generic` | HTTP, SSL | -- |
+| `mokowaas` | HTTP, SSL | Version, updates, extensions, backup (via Joomla API) |
+| `mokowaas-dev` | HTTP, SSL | Same as mokowaas |
+| `mokowaas-demo` | HTTP, SSL | Same as mokowaas |
+| `mokocrm` | HTTP, SSL | Planned |
+| `mokocrm-dev` | HTTP, SSL | Planned |
+| `mokocrm-demo` | HTTP, SSL | Planned |
+| `other` | HTTP, SSL | -- |
 
 ## Multiple endpoints per client
 
 A single client can have multiple monitored endpoints sharing the same `client` label:
 
 ```json
-{"name": "acme-live", "url": "https://acme.com", "type": "joomla", "client": "ACME"},
-{"name": "acme-dev",  "url": "https://acme.dev.mokoconsulting.tech", "type": "joomla", "client": "ACME", "tlsVerify": false},
-{"name": "acme-staging", "url": "https://acme-staging.com", "type": "joomla", "client": "ACME"}
+{"name": "acme-live", "url": "https://acme.com", "type": "mokowaas", "client": "ACME"},
+{"name": "acme-dev",  "url": "https://acme.dev.mokoconsulting.tech", "type": "mokowaas-dev", "client": "ACME", "tlsVerify": false},
+{"name": "acme-staging", "url": "https://acme-staging.com", "type": "mokowaas", "client": "ACME"}
 ```
 
 Grafana dashboard dropdowns auto-populate from Prometheus `site_name` and `site_type` labels.
@@ -83,7 +85,7 @@ Grafana dashboard dropdowns auto-populate from Prometheus `site_name` and `site_
 generate-targets.sh --deploy
 ```
 
-The `--deploy` flag now also auto-creates Grafana dashboards (one per client) via the Grafana API. Dashboard UIDs are stable (derived from client name hash), so re-running updates existing dashboards rather than creating duplicates.
+The `--deploy` flag also auto-creates Grafana dashboards via the Grafana API. Dashboard UIDs are stable (derived from client name hash), so re-running updates existing dashboards rather than creating duplicates.
 
 ## Template-Client-WaaS workflow files
 
@@ -96,8 +98,8 @@ The client template repo (`Template-Client-WaaS`) includes two Gitea Actions wor
 
 ## Related
 
-- [SITE_MONITORING](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki/SITE_MONITORING) -- full architecture docs in moko-platform wiki
-- [JOOMLA_SYNC](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki/JOOMLA_SYNC) -- SFTP sync between dev/live servers
+- [SITE_MONITORING](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki/SITE_MONITORING) — full architecture docs in moko-platform wiki
+- [JOOMLA_SYNC](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki/JOOMLA_SYNC) — SFTP sync between dev/live servers
 ]]>
 
 ---
@@ -107,3 +109,4 @@ The client template repo (`Template-Client-WaaS`) includes two Gitea Actions wor
 | Revision | Date | Author | Description |
 |---|---|---|---|
 | 1.0 | 2026-05-09 | Moko Consulting | Initial version |
+| 1.1 | 2026-05-12 | Moko Consulting | Update site types to mokowaas/mokocrm/other |