fixing carriage return necessary for details not to breka in console view (#948)

Co-authored-by: jdv <julien@crowdsec.net>

Author: rr404

crowdsec-docs/unversioned/troubleshooting/issue_lp_no_logs_parsed.md

@@ -33,6 +33,7 @@ sudo cscli metrics show acquisition parsers
 ```bash
 docker exec crowdsec cscli metrics show acquisition parsers
 ```
+
 ```bash
 kubectl exec -n crowdsec -it <agent-pod> -- cscli metrics show acquisition parsers
 ```

crowdsec-docs/unversioned/troubleshooting/issue_lp_no_logs_read.md

@@ -62,9 +62,11 @@ sudo cscli metrics show acquisition
 ```bash
 docker exec crowdsec cscli metrics show acquisition
 ```
+
 ```bash
 kubectl exec -n crowdsec -it <agent-pod> -- cscli metrics show acquisition
 ```
+
 </details>
 
 **What to look for:**

crowdsec-docs/unversioned/troubleshooting/issue_lp_offline.md

@@ -40,9 +40,11 @@ Or [check the logs](/u/troubleshooting/security_engine#where-are-the-logs-stored
 ```bash
 docker ps --filter name=crowdsec
 ```
+
 ```bash
 kubectl get pods -n crowdsec
 ```
+
 </details>
 
 On the LAPI node, run `sudo cscli machines list` and check whether the `Last Update` column is older than 24 hours for the affected machine.
@@ -61,9 +63,11 @@ sudo systemctl restart crowdsec
 ```bash
 docker restart crowdsec
 ```
+
 ```bash
 kubectl rollout restart deployment/crowdsec -n crowdsec
 ```
+
 </details>
 
 After the restart, verify the agent is checking in:
@@ -100,9 +104,11 @@ sudo cscli machines list
 ```bash
 docker exec crowdsec cscli machines list
 ```
+
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli machines list
 ```
+
 </details>
 
 - If the machine shows in `PENDING` state or is missing entirely, credentials need validation

crowdsec-docs/unversioned/troubleshooting/issue_se_no_alerts.md

@@ -37,12 +37,15 @@ sudo cscli collections list
 ```
 <details>
    <summary>Run this command for Docker or Kubernetes</summary>
+
 ```bash
 docker exec crowdsec cscli collections list
 ```
+
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli collections list
 ```
+
 </details>
 
 Compare your installed collections against your actual services (nginx, apache, ssh, etc.). Missing collections means no detection rules for those services.
@@ -76,6 +79,7 @@ sudo systemctl reload crowdsec
 ```bash
 docker exec crowdsec cscli collections install crowdsecurity/nginx
 ```
+
 ```bash
 docker restart crowdsec
 ```
@@ -84,9 +88,11 @@ docker restart crowdsec
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli collections install crowdsecurity/nginx
 ```
+
 ```bash
 kubectl rollout restart deployment/crowdsec -n crowdsec
 ```
+
 </details>
 
 ### Events massively whitelisted
@@ -107,10 +113,12 @@ sudo cscli metrics show acquisition
 ```bash
 docker exec crowdsec cscli metrics show scenarios
 ```
+
 **Kubernetes**
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli metrics show scenarios
 ```
+
 </details>
 
 **Look at the Lines whitelisted column**
@@ -157,6 +165,7 @@ docker exec crowdsec cscli simulation status
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli simulation status
 ```
+
 </details>
 
 If scenarios are listed, they're in simulation mode and won't be sent to CrowdSec console (they should however still appear in `cscli alerts list`).
@@ -176,6 +185,7 @@ sudo systemctl reload crowdsec
 ```bash
 docker exec crowdsec cscli simulation disable --all
 ```
+
 ```bash
 docker restart crowdsec
 ``
@@ -184,9 +194,11 @@ docker restart crowdsec
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli simulation disable --all
 ```
+
 ```bash
 kubectl rollout restart deployment/crowdsec -n crowdsec
 ```
+
 </details>
 
 You can also disable simulation for specific scenarios only:
@@ -219,10 +231,12 @@ sudo cscli metrics show acquisition parsers
 ```bash
 docker exec crowdsec cscli metrics show acquisition parsers
 ```
+
 **Kubernetes**
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli metrics show acquisition parsers
 ```
+
 </details>
 
 Look at "Lines parsed" - if this number is very low (dozens or hundreds per day), you may simply have insufficient traffic volume for malicious activity to appear.
@@ -245,6 +259,7 @@ sudo cscli metrics show bouncers
 ```bash
 docker exec crowdsec cscli decisions list
 ```
+
 ```bash
 docker exec crowdsec cscli metrics show bouncers
 ```
@@ -253,9 +268,11 @@ docker exec crowdsec cscli metrics show bouncers
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli decisions list
 ```
+
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli metrics show bouncers
 ```
+
 </details>
 
 High numbers of active decisions or bouncer blocks may indicate your proactive defenses are effectively blocking all malicious actors. However lets make sure no other issues

crowdsec-docs/unversioned/troubleshooting/issue_se_offline.md

@@ -34,10 +34,12 @@ sudo journalctl -u crowdsec -n 50
 
 <details>
    <summary>Run this command for Docker or Kubernetes</summary>
+
 ```bash
 docker ps --filter name=crowdsec
 kubectl get pods -n crowdsec
 ```
+
 </details>
 
 If the host itself is unreachable (hypervisor, VM, or cloud instance down), the Console cannot receive a heartbeat and marks the engine offline.
@@ -52,6 +54,7 @@ sudo systemctl restart crowdsec
 
 <details>
    <summary>For Docker or Kubernetes</summary>
+
 **Docker:**
 ```bash
 docker restart crowdsec
@@ -61,6 +64,7 @@ docker restart crowdsec
 ```bash
 kubectl rollout restart deployment/crowdsec -n crowdsec
 ```
+
 </details>
 
 After restarting, re-run `sudo cscli console status` to ensure the heartbeat is restored.

crowdsec-docs/unversioned/troubleshooting/issue_se_too_many_alerts.md

@@ -41,10 +41,12 @@ Docker
 ```bash
 docker exec crowdsec cscli alerts list -l 100
 ```
+
 Kubernetes
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli alerts list -l 100
 ```
+
 </details>
 
 2. Look for patterns:
@@ -61,15 +63,15 @@ sudo cscli metrics show scenarios
 
 <details>
    <summary>Run this command for Docker or Kubernetes</summary>
-Docker
+
 ```bash
 docker exec crowdsec cscli metrics show scenarios
 ```
 
-Kubernetes
 ```bash
 kubectl exec -n crowdsec -it $(kubectl get pods -n crowdsec -l type=lapi -o name) -- cscli metrics show scenarios
 ```
+
 </details>
 
 Look for scenarios with extremely high "Overflow" counts or "Current count" numbers.