docs(all): fix markdown syntax and snippets

docs/services/common/alloy.md

@@ -2,7 +2,7 @@
 
 ## Communication
 
-Alloy runs on systemd \(host\), and postgresql runs as container \(rootless podman\). When host system and container communicate, container recognizes host system as host-gateway \(Link local address\).
+Alloy runs on systemd (host), and postgresql runs as container (rootless podman). When host system and container communicate, container recognizes host system as host-gateway (Link local address).
 
 ## postgresql monitor
  

docs/services/common/caddy.md

@@ -6,10 +6,10 @@ This is not a perfect E2EE communication theorogically, however technically it i
 
 ### .com public domain
 
-WAN - \(Let's Encrypt certificate\) -> Caddy \(auth\) - \(ilnmors internal certificate\) -> Caddy \(app\) or https services - http -> app's local service
+WAN - (Let's Encrypt certificate) -> Caddy (auth) - (ilnmors internal certificate) -> Caddy (app) or https services - http -> app's local service
 
 ### .internal private domain
-client - \(ilnmors internal certificate\) -> Caddy \(Infra\) - http -> local services
+client - (ilnmors internal certificate) -> Caddy (Infra) - http -> local services
 
 ### DNS record
 

docs/services/common/crowdsec.md

@@ -3,16 +3,16 @@
 ## LAPI
 
 ### Detecting
-Host logs \> CrowdSec Agent\(parser\) > CrowdSec LAPI
+Host logs > CrowdSec Agent(parser) > CrowdSec LAPI
 
 ### Decision
-CrowdSec LAPI \(Decision + Register\)
+CrowdSec LAPI (Decision + Register)
 
 ### Block
-CrowdSec LAPI \> CrowdSec Bouncer \(Block\)
+CrowdSec LAPI > CrowdSec Bouncer (Block)
 
 ## CAPI
-CrowdSec CAPI \> crowdsec LAPI \(local\) \> CrowdSec Bouncer \(Block\)
+CrowdSec CAPI > crowdsec LAPI (local) > CrowdSec Bouncer (Block)
 
 ## Ansible Deployment
 
@@ -20,34 +20,34 @@ CrowdSec CAPI \> crowdsec LAPI \(local\) \> CrowdSec Bouncer \(Block\)
 
 - Deploy fw's config.yaml
 - Deploy crowdsec certificates
-- Register machines \(Agents\)
-- Register bouncers \(Bouncers\)
+- Register machines (Agents)
+- Register bouncers (Bouncers)
 
 ### Set Bouncer (fw/roles/tasks/set_crowdsec_bouncer.yaml)
 
 - Deploy crowdsec-firewall-bouncer.yaml
-- Install suricata collection \(parser\) with cscli
+- Install suricata collection (parser) with cscli
 - Set acquis.d for suricata
 - set-only: bouncer can't get metrics from the chain and rules count result which it doesn't make. - It means, it is impossible to use prometheus metric with set-only true option.
 - chain or rules matched count reasults are able to check on nftables. 
-  - use sudo nft list chain inet filter global to check packet blocked. \(counter command is required\)
+  - use sudo nft list chain inet filter global to check packet blocked. (counter command is required)
 
 ### Set Machines; agents (common/tasks/set_crowdsec_agent.yaml)
 
-- Deploy config.yaml except fw \(disable LAPI, online_api_credentials\)
+- Deploy config.yaml except fw (disable LAPI, online_api_credentials)
 - Deploy local_api_credentials.yaml
 
 ### Set caddy host (auth/tasks/set_caddy.yaml)
 
 - Set caddy CrowdSec module
 - Set caddy log directory
-- Install caddy collection \(parser\) with cscli
+- Install caddy collection (parser) with cscli
 - Set acquis.d for caddy
 
 ### Set whitelist (/etc/crowdsec/parser/s02-enrich/whitelists.yaml)
 
 - Set only local console IP address
-- This can block local VM to the other subnet, but the communication between vms is possible because they are in the same subnet\(L2\) - packets don't pass the fw.
+- This can block local VM to the other subnet, but the communication between vms is possible because they are in the same subnet(L2) - packets don't pass the fw.
 - Crowdsec bouncer only conducts blocks forward chain which pass Firewall, it is blocked by crowdsec bouncer based on lapi
 
 ## Test

docs/services/common/kopia.md

@@ -10,5 +10,5 @@ Kopia saves all information, even the users and policies on repository. Reposito
 
 When kopia is run as a kopia server, client can access to server with user and user password. The clients don't have to know master password. Kopia server decrypt the repository with the master password, and the client just access to the kopia server with their user account.
 
-Repository \<- Master password -\> Kopia server \<- User password -\> Kopia client
+Repository <- Master password -> Kopia server <- User password -> Kopia client