ok summary jsut need space :D

Author: jdv

crowdsec-docs/unversioned/getting_started/healthcheck.mdx

@@ -27,7 +27,8 @@ The HTTP collection and the Linux collection contain **dummy scenarios** allowin
 :::
 
 <details>
-  <summary>Test HTTP detection</summary>
+  <summary>☑️ Test **HTTP** detection</summary>
+  
 Let's trigger the `crowdsecurity/http-generic-test` dummy scenario by calling a *probe path* on your web server.
 
 1️⃣ Request your service URL with the following path: `/crowdsec-test-NtktlJHV4TfBSK3wvlhiOBnl`
@@ -37,11 +38,15 @@ Let's trigger the `crowdsecurity/http-generic-test` dummy scenario by calling a
 
 <CodeBlock className="language-bash">sudo cscli alerts list -s crowdsecurity/http-generic-test</CodeBlock>
 
-Note that this scenario has a delay of 5 minutes before it can re-trigger _(blackhole parameter of the scenario)_. 
+Notes:
+- If it's done from a private IP the alert won't appear as private IPs are whitelisted by default.
+  - You can call the test url via a browser if you prefer, it might make it easier to test from an other device.
+- This scenario has a delay of 5 minutes before it can re-trigger _(blackhole parameter of the scenario)_. 
 </details>
 
 <details>
-    <summary>Test SSH detection</summary>
+    <summary>☑️ Test **SSH** detection</summary>
+
 Let's trigger the `crowdsecurity/ssh-generic-test` dummy scenario by logging in to your server via SSH with a specific user.
 
 1️⃣ Try to authenticate to your server via SSH using the following user: `crowdsec-test-NtktlJHV4TfBSK3wvlhiOBnl`.
@@ -55,7 +60,8 @@ Note that this scenario has a delay of 5 minute before it can re-trigger _(black
 </details>
 
 <details>
-    <summary>Test CrowdSec WAF with an AppSec detection</summary>
+    <summary>☑️ Test CrowdSec WAF with an **AppSec** detection</summary>
+
 If you are using an AppSec-capable bouncer and have configured CrowdSec WAF, you can test the detection of an AppSec scenario.
 It's similar to the HTTP detection test, but it will trigger `crowdsecurity/appsec-generic-test`.
 
@@ -81,7 +87,7 @@ If so, you can proceed to the next phase of the health check: [**Connectivity ch
 If not, check the troubleshooting section below
 
 <details>
-    <summary>🚨 Detection Troubleshooting</summary>
+    <summary>🚨 **Detection Troubleshooting**</summary>
 
   *No alerts triggered? Let's investigate: Here are some tests to identify where the issue might be.*