chore: reverted monitor/architecture changes

Author: stevedylandev

content/monitor/architecture.mdx

@@ -13,6 +13,14 @@ OpenZeppelin Monitor is organized as a data processing pipeline that spans from
 The diagram below shows the core processing pipeline of OpenZeppelin Monitor, from blockchain networks and configuration through to notification channels:
 
 ```mermaid
+%%{init: {
+    'theme': 'base',
+    'themeVariables': {
+        'background': '#ffffff',
+        'mainBkg': '#ffffff',
+        'primaryBorderColor': '#cccccc'
+    }
+}}%%
 flowchart LR
     subgraph "Blockchain Networks"
         EVMN["EVM Networks"]
@@ -72,6 +80,14 @@ The system consists of several core services that are initialized at startup and
 ### Service Initialization Flow
 
 ```mermaid
+%%{init: {
+    'theme': 'base',
+    'themeVariables': {
+        'background': '#ffffff',
+        'mainBkg': '#ffffff',
+        'primaryBorderColor': '#cccccc'
+    }
+}}%%
 graph TD
     subgraph Entry Point
         MAIN[main.rs]
@@ -195,6 +211,14 @@ The following table describes the key responsibilities of each service in the Op
 The following _runtime flow_ illustrates how data moves through the system, from blockchain networks to notification channels. This sequence represents the core monitoring loop that executes for each configured network.
 
 ```mermaid
+%%{init: {
+    'theme': 'base',
+    'themeVariables': {
+        'background': '#ffffff',
+        'mainBkg': '#ffffff',
+        'primaryBorderColor': '#cccccc'
+    }
+}}%%
 sequenceDiagram
     participant BWS as BlockWatcherService
     participant BS as BlockStorage
@@ -316,7 +340,7 @@ The system implements comprehensive validation:
 
 
 
-For configuration examples and best practices, see the [Configuration Guidelines](/monitor#configuration-guidelines) section in the user documentation.
+For configuration examples and best practices, see the [Configuration Guidelines](#configuration-guidelines) section in the user documentation.
 
 
 ## Extensibility Points