Remove manual text formatting

Signed-off-by: Pau Capdevila <[email protected]>

Author: pau-hedgehog

docs/architecture/management.md

@@ -42,27 +42,27 @@ FC -->|Watches CRs| K8S
 
 ---
 
-## **Management Workflow Overview**
+## Management Workflow Overview
 
-### **User**
-- **Creates Fabric CR YAMLs** and applies them through standard Kubernetes resource management.
-- **Uses [`kubectl`](https://kubernetes.io/docs/reference/kubectl/) and `kubectl fabric`** to interact with the Kubernetes API for fabric resource management.
-    - Can use their **own `kubectl` installation** or the one pre-installed on the control node as part of [k3s](https://k3s.io).
+### User
+- Creates Fabric CR YAMLs and applies them through standard Kubernetes resource management.
+- Uses [`kubectl`](https://kubernetes.io/docs/reference/kubectl/) and `kubectl fabric` to interact with the Kubernetes API for fabric resource management.
+    - Can use their own `kubectl` installation or the one pre-installed on the control node as part of [k3s](https://k3s.io).
 
-### **Kubernetes API Server (K8S)**
+### Kubernetes API Server (K8S)
 - Part of [Kubernetes](https://kubernetes.io).
-- Manages Fabric Custom Resources (CRs) and interacts with the **Fabric Controller**.
+- Manages Fabric Custom Resources (CRs) and interacts with the Fabric Controller.
 
-### **kubectl & kubectl fabric**
+### kubectl & kubectl fabric
 - [`kubectl`](https://kubernetes.io/docs/reference/kubectl/) is the standard CLI tool for [Kubernetes](https://kubernetes.io).
 - `kubectl fabric` is a plugin that extends `kubectl` with fabric-specific commands and interacts with the Kubernetes API Server. It supports the following commands:
-    - **vpc** – Manage VPCs: create, attach, peer, or wipe all related resources
-    - **switch** – Manage switches: get IP, SSH, serial, reboot, reinstall
-    - **connection** – View connections: management, fabric, vpc-loopback
-    - **switchgroup** – Create SwitchGroups
-    - **external** – Manage external BGP peers and VPC peering
-    - **wiring** – Export fabric wiring diagrams
-    - **inspect** – Inspect and troubleshoot fabric resources:
+    - vpc – Manage VPCs: create, attach, peer, or wipe all related resources
+    - switch – Manage switches: get IP, SSH, serial, reboot, reinstall
+    - connection – View connections: management, fabric, vpc-loopback
+    - switchgroup – Create SwitchGroups
+    - external – Manage external BGP peers and VPC peering
+    - wiring – Export fabric wiring diagrams
+    - inspect – Inspect and troubleshoot fabric resources:
         - `fabric` – Overview of control nodes and switches
         - `switch`, `port` – Status, counters, and usage
         - `server`, `connection` – VPC/external attachments and link details
@@ -71,30 +71,30 @@ FC -->|Watches CRs| K8S
         - `ip`, `mac` – Lookup usage across the fabric
         - `access` – Check reachability between VPCs, servers, and IPs
 
-### **Fabricator**
-- Using the **hhfab** CLI you can **SSH** the control node and use **K9s** or **kubectl** and **kubectl fabric** to manage or monitor Fabric API objects.
+### Fabricator
+- Using the hhfab CLI you can SSH the control node and use K9s or kubectl and kubectl fabric to manage or monitor Fabric API objects.
 
-### **K9s**
+### K9s
 - K9s is a terminal based Kubernetes UI that provides visibility and control over Kubernetes resources, allowing you to manage pods, nodes, services, logs, and Fabric resources efficiently. It includes some helper plugins:
-    - **SSH** – SSH into a fabric switch
-    - **Serial** – Open a serial connection to a fabric switch
-    - **Reboot** – Reboot a fabric switch
-    - **Power Reset** Perform a power reset on a fabric switch in the NOS
-    - **Reinstall** – Reinstall a fabric switch
+    - SSH – SSH into a fabric switch
+    - Serial – Open a serial connection to a fabric switch
+    - Reboot – Reboot a fabric switch
+    - Power Reset Perform a power reset on a fabric switch in the NOS
+    - Reinstall – Reinstall a fabric switch
 
 ---
 
-## **GitOps Integration**
+## GitOps Integration
 
 GitOps is a continuous deployment approach where the desired state of a Kubernetes cluster is stored in Git. A GitOps controller monitors this repository and ensures the actual cluster state matches the declared state, using the Kubernetes API.
 
 Hedgehog Fabric is fully compatible with GitOps workflows and can be managed declaratively using any GitOps-compatible tool such as [ArgoCD](https://argo-cd.readthedocs.io/en/stable/) or [Flux](https://fluxcd.io).
 
-- **User Responsibilities:**
+- User Responsibilities:
     - Define Fabric Custom Resources (CRs) in YAML.
     - Commit and push these CRs to a [Git repository](https://git-scm.com) for version control and collaboration.
 
-- **GitOps Tool Responsibilities:**
+- GitOps Tool Responsibilities:
     - Monitor the Git repository for updates.
     - Apply changes to the cluster automatically via the Kubernetes API Server.
 

docs/architecture/overview.md

@@ -4,7 +4,7 @@ This section provides an architectural understanding of Hedgehog Open Network Fa
 
 Hedgehog Open Network Fabric leverages the Kubernetes API to manage its resources. All user-facing APIs are exposed as Kubernetes Custom Resources Definitions (CRDs), allowing users to manage Fabric resources using standard Kubernetes tools.
 
-To make network switches Kubernetes-aware, the Fabric employs an **Agent** running on each switch. This agent acts as an interface  between the Kubernetes control plane and the switch internal network configuration mechanisms. It continuously syncs desired state from Kubernetes via the Fabric Controller and applies configurations using **gNMI** (gRPC Network Management Interface).
+To make network switches Kubernetes-aware, the Fabric employs an Agent running on each switch. This agent acts as an interface  between the Kubernetes control plane and the switch internal network configuration mechanisms. It continuously syncs desired state from Kubernetes via the Fabric Controller and applies configurations using gNMI (gRPC Network Management Interface).
 
 ## Components
 
@@ -70,38 +70,38 @@ graph TD;
 The key components essential for understanding the Fabric architecture are:
 
 ### Control Node Components
-- **Fabric Controller**: The central control plane component that manages Fabric resources and configurations.
-- **Fabric CLI (kubectl plugin)**: A `kubectl` plugin that provides an easy way to manage Fabric resources.
-- **Fabric Proxy**: A pod responsible for collecting logs and metrics from switches (via Alloy) and forwarding them to an external system.
-- **Fabricator**: A tool for installing and configuring Fabric, including virtual lab environments.
+- Fabric Controller: The central control plane component that manages Fabric resources and configurations.
+- Fabric CLI (kubectl plugin): A `kubectl` plugin that provides an easy way to manage Fabric resources.
+- Fabric Proxy: A pod responsible for collecting logs and metrics from switches (via Alloy) and forwarding them to an external system.
+- Fabricator: A tool for installing and configuring Fabric, including virtual lab environments.
 
 ### SONiC Switch Components
-- **Fabric Agent**: Runs on each switch and applies configurations received from the control plane.
-- **Alloy**: Collects logs and telemetry data from the switch.
-- **gNMI Interface**: The main configuration API used by the Fabric Agent to interact with the switch.
-- **Config DB**: The central database in SONiC responsible for maintaining switch configuration.
-- **ASIC**: The hardware component handling packet forwarding.
+- Fabric Agent: Runs on each switch and applies configurations received from the control plane.
+- Alloy: Collects logs and telemetry data from the switch.
+- gNMI Interface: The main configuration API used by the Fabric Agent to interact with the switch.
+- Config DB: The central database in SONiC responsible for maintaining switch configuration.
+- ASIC: The hardware component handling packet forwarding.
 
 The SONiC architecture presented here is a high-level abstraction, for simplicity.
 
 ## Architecture Flow
 
-### 1. **Fabric Installation & Configuration**
-- The **Fabricator** tool installs and configures Hedgehog Fabric.
-- It provisions **Flatcar Linux** for Control Nodes and automatically installs **K3s** (lightweight Kubernetes).
+### 1. Fabric Installation & Configuration
+- The Fabricator tool installs and configures Hedgehog Fabric.
+- It provisions Flatcar Linux for Control Nodes and automatically installs K3s (lightweight Kubernetes).
 - All components, including their dependencies, are deployed within Kubernetes.
 
-### 2. **Fabric API & Resource Management**
-- Hedgehog represents all infrastructure elements as **Fabric resources** using Kubernetes CRDs.
-- These CRDs define **switches, servers, control nodes, external systems, and their interconnections**.
-- The **Fabric Controller** watches these CRDs and manages configurations accordingly.
+### 2. Fabric API & Resource Management
+- Hedgehog represents all infrastructure elements as Fabric resources using Kubernetes CRDs.
+- These CRDs define switches, servers, control nodes, external systems, and their interconnections.
+- The Fabric Controller watches these CRDs and manages configurations accordingly.
 
-### 3. **Switch Configuration & Management**
-- The **Fabric Controller** communicates with the **Fabric Agent** on each switch via the Kubernetes API.
-- The **Fabric Agent** applies configurations using the **gNMI** interface, updating the **Config DB**.
-- The **Config DB** ensures that all settings are applied to the **ASIC** for packet forwarding.
+### 3. Switch Configuration & Management
+- The Fabric Controller communicates with the Fabric Agent on each switch via the Kubernetes API.
+- The Fabric Agent applies configurations using the gNMI interface, updating the Config DB.
+- The Config DB ensures that all settings are applied to the ASIC for packet forwarding.
 
-### 4. **Telemetry & Monitoring**
-- The **Alloy** agent on the switch collects logs and metrics.
-- Logs and metrics are sent to the **Fabric Proxy** running in Kubernetes.
-- The **Fabric Proxy** forwards this data to **LGTM**, an external logging and monitoring system.
+### 4. Telemetry & Monitoring
+- The Alloy agent on the switch collects logs and metrics.
+- Logs and metrics are sent to the Fabric Proxy running in Kubernetes.
+- The Fabric Proxy forwards this data to LGTM, an external logging and monitoring system.