Update documentation for clarity and formatting improvements

Author: devanshjainms

docs/ARCHITECTURE.md

@@ -9,8 +9,6 @@
 - **WORKSPACES**: System-specific configuration and credentials management
 - **Reporting Engine**: Generates detailed HTML test reports
 
-
-
 ## Architecture
 
 ### High-Level Framework Structure
@@ -81,7 +79,8 @@ graph TB
 ```
 
 ## Directory Structure
-```
+
+```plain
 src/
 ├── module_utils/          # Shared utilities and constants
 ├── modules/              # Custom Ansible modules
@@ -119,4 +118,4 @@ sequenceDiagram
         Framework->>Reporting: Generate Failure Report
         Reporting-->>User: Failure Report
     end
-```
+```

docs/DB_HIGH_AVAILABILITY.md

@@ -16,4 +16,4 @@
 | Secondary Node Kill | Process | The Secondary Node Kill test examines cluster resilience by forcefully terminating HANA processes on the secondary node using the kill -9 signal. The test validates that the primary node maintains normal operation while the secondary node undergoes recovery, ensuring cluster stability and proper data synchronization after the recovery process completes. | [node-kill.md](./pseudocode/node-kill.md) |
 | Secondary Echo B | System | The Secondary Echo B test simulates an uncontrolled system crash on the secondary HANA node by executing the 'echo b' command, triggering an immediate reboot without proper shutdown procedures. The test validates that the primary node maintains operation, verifies cluster stability, and ensures system replication resumes correctly after the secondary node recovers. | [echo-b.md](./pseudocode/echo-b.md) |
 | Filesystem Freeze | Storage | The Filesystem Freeze test validates cluster behavior when the primary node's filesystem becomes unresponsive. It simulates a storage issue by freezing the filesystem on the primary node running HANA database, which triggers automatic failover to the secondary node. The test verifies proper cluster reaction, resource migration, and data consistency after recovery. | [freeze-filesystem.md](./pseudocode/freeze-filesystem.md) |
-| SBD Fencing | Fencing | Validates cluster fencing mechanism by killing the SBD inquisitor process on the primary node. Tests proper fence detection, node isolation, and automated failover to ensure cluster integrity during hardware or communication failures. | [sbd-fencing.md](./pseudocode/sbd-fencing.md) |
+| SBD Fencing | Fencing | Validates cluster fencing mechanism by killing the SBD inquisitor process on the primary node. Tests proper fence detection, node isolation, and automated failover to ensure cluster integrity during hardware or communication failures. | [sbd-fencing.md](./pseudocode/sbd-fencing.md) |

docs/HIGH_AVAILABILITY.md

@@ -32,7 +32,7 @@ In summary, SAP High Availability testing is an integral part of the overall SAP
 
 #### Optional Components
 
-- **Analytics Integration** [Telemetry Setup Information](./docs/TELEMETRY_SETUP.md)
+- **Analytics Integration** [Telemetry Setup Information](./TELEMETRY_SETUP.md)
   - Azure Log Analytics
   - Azure Data Explorer
 
@@ -232,4 +232,4 @@ cd WORKSPACES/SYSTEM/<SYSTEM_CONFIG_NAME>/quality_assurance/
 
 ## Additional Resources
 
-- [Azure SAP Documentation](https://docs.microsoft.com/azure/sap)
+- [Azure SAP Documentation](https://docs.microsoft.com/azure/sap)

docs/TELEMETRY_SETUP.md

@@ -7,7 +7,7 @@ This guide outlines the steps to create an Azure Data Explorer (Kusto) cluster a
 ## Azure Data Explorer (Kusto) Cluster Setup
 
 1. **Log in to the Azure Portal:**  
-   Navigate to https://portal.azure.com and sign in with your Azure credentials.
+   Navigate to [Azure Portal](https://portal.azure.com) and sign in with your Azure credentials.
 
 2. **Create a Resource Group:**  
    - Click on "Resource groups" in the left navigation pane.  
@@ -43,12 +43,12 @@ This guide outlines the steps to create an Azure Data Explorer (Kusto) cluster a
     - **adx_cluster_fqdn:** Azure Data Explorer Cluster FQDN [Data Ingestion URI].
     - **adx_database_name:** Azure Data Explorer Database Name [Database Name]
     - **adx_client_id:** Azure Data Explorer Client ID [MSI Client ID]
-    - **telemetry_table_name:** Name of the table in the ADX database [SAP_AUTOMATION_QA]
+    - **telemetry_table_name:** Name of the table in the ADX database SAP_AUTOMATION_QA
 
 ## Azure Log Analytics Workspace Setup
 
 1. **Log in to the Azure Portal:**  
-   Use https://portal.azure.com with your credentials.
+   Login to [Azure Portal](https://portal.azure.com) with your credentials.
 
 2. **Create a Resource Group (if needed):**  
    If you haven't already created a resource group for Log Analytics, follow the same step as above.
@@ -65,7 +65,7 @@ This guide outlines the steps to create an Azure Data Explorer (Kusto) cluster a
 4. **Assign Azure Roles for Data Ingestion:**  
    To ingest or work with data in a Log Analytics Workspace, assign the following roles:
    - **Log Analytics Contributor:** Grants permissions to submit and manage data in the workspace.
-   
+
    To assign a role:
    - Navigate to the Log Analytics Workspace resource.
    - Click on "Access control (IAM)."  
@@ -75,4 +75,4 @@ This guide outlines the steps to create an Azure Data Explorer (Kusto) cluster a
 5. **Parameters**
     - **laws_workspace_id:** Log Analytics Workspace ID [Workspace ID]
     - **laws_shared_key:** Log Analytics Shared Key [Primary Key]
-    - **telemetry_table_name:** Name of the table in Log Analytics [SAP_AUTOMATION_QA]
+    - **telemetry_table_name:** Name of the table in Log Analytics SAP_AUTOMATION_QA