Address the following comment on docs/alerts/alert-configuration-syntax/variables-and-special-symbols.md at line 5:<comment>The `:::tip` block that explains why status values are 1/3/4 is never closed before the following `:::note`, so the admonition markup is unbalanced and renders incorrectly.</comment><file context>@@ -0,0 +1,607 @@++Alert expressions in Netdata can reference variables that represent metric values, alert state, time information, and chart metadata. Understanding which variables are available and how to discover them is essential for writing effective alerts.++:::tip++Refer to this section when you&#39;re writing `calc`, `warn`, or `crit` expressions and need to know which variables exist, debugging alerts that reference missing or incorrect variable names, building alerts that combine multiple dimensions or chart metadata, or using the `alarm_variables` API to explore what&#39;s available on a chart.</file context>

Address the following comment on docs/alerts/alert-configuration-syntax/variables-and-special-symbols.md at line 127:<comment>`calc` converts `$mem_raw` into a boolean, so `$this` is never above 4M and the example alert can never fire.</comment><file context>@@ -0,0 +1,607 @@+**Example:**+```conf+on: system.mem+calc: $mem_raw &gt; 5000000  # Raw collected value in KiB+warn: $this &gt; 4000000+```</file context>

Address the following comment on docs/alerts/alert-configuration-syntax/calculations-and-transformations.md at line 92:<comment>This example adds a critical threshold that the underlying stock alert does not define, so the doc is attributing behavior that doesn’t exist.</comment><file context>@@ -0,0 +1,352 @@+  calc: $this / 1024 * 100 / ( $system.ram.used + $system.ram.cached + $system.ram.free )+ units: MB/s+  warn: $this &gt; 200+  crit: $this &gt; 400+```+</file context>

Address the following comment on docs/alerts/alert-configuration-syntax/calculations-and-transformations.md at line 91:<comment>The documented warning threshold (`$this &gt; 200`) does not match the real stock alert, which warns once the percentage exceeds roughly 20–30; documenting the wrong cutoff misleads anyone copying the example.</comment><file context>@@ -0,0 +1,352 @@+lookup: sum -30m unaligned absolute of out+  calc: $this / 1024 * 100 / ( $system.ram.used + $system.ram.cached + $system.ram.free )+ units: MB/s+  warn: $this &gt; 200+  crit: $this &gt; 400+```</file context>

Address the following comment on docs/alerts/alert-configuration-syntax/calculations-and-transformations.md at line 90:<comment>The swap alert example labels the result as `MB/s`, but the stock alert actually reports a percentage of RAM swapped out, so the documented units are incorrect.</comment><file context>@@ -0,0 +1,352 @@+# From swap.conf+lookup: sum -30m unaligned absolute of out+  calc: $this / 1024 * 100 / ( $system.ram.used + $system.ram.cached + $system.ram.free )+ units: MB/s+  warn: $this &gt; 200+  crit: $this &gt; 400</file context>

Address the following comment on docs/alerts/alert-configuration-syntax/optional-metadata.md at line 193:<comment>Section 3.6.6 Step 2 recommends `type` values like `latency`/`error`, contradicting the earlier definition of `type` as a functional domain (System, Database, etc.), which will confuse alert authors.</comment><file context>@@ -0,0 +1,246 @@++2. **Define recommended `type` values aligned with your SRE vocabulary**+   +   Example: `latency`, `error`, `saturation`, `traffic`, `anomaly`++3. **Map `component` values to your services or teams**</file context>

Address the following comment on docs/alerts/creating-alerts-pages/creating-and-editing-alerts-via-config-files.md at line 166:<comment>Chart IDs are documented as never using underscores even though real Netdata chart IDs (for example `disk_space._run`) contain underscores; this misleads readers trying to locate the correct `chart` name.</comment><file context>@@ -0,0 +1,362 @@+- **Dashboard:** Hover over the date on a chart and check the tooltip+- **API:** `curl &quot;http://localhost:19999/api/v1/charts&quot; | jq &#39;.charts[] | {id, context}&#39;`++Both use dots (`.`), not underscores (`_`), in their names.++:::</file context>