Fix format

Author: VietND96

website_and_docs/content/blog/2026/selenium-grid-4-41-deep-dive.md

@@ -145,7 +145,7 @@ spec:
             claimName: selenium-assets
 ```
 
-Event bus connectivity (host, ports, registration secret) is passed as environment variables. Browser stereotypes and Kubernetes-specific tuning (`termination-grace-period`, `assets-path`, resource overrides) live entirely in the TOML file inside the ConfigMap, keeping them independently updatable without redeploying the Node.
+Event bus connectivity (host), and node config (session timeout) are passed as environment variables. Browser stereotypes live entirely in the TOML file inside the ConfigMap, keeping them independently updatable without redeploying the Node.
 
 The [RBAC manifest](https://github.com/SeleniumHQ/docker-selenium/blob/4.41.0-20260222/kubernetes/DynamicGrid/BaseConfig/rbac.yaml) grants the Node the minimal permissions needed — `create`, `delete`, and `get` on `pods` and `pods/log` in the configured namespace. No cluster-wide permissions needed.
 
@@ -158,21 +158,21 @@ This means the browser Pods land on exactly the same node pool, zone, or hardwar
 The practical implication: you can deploy **multiple Dynamic Grid Nodes**, each pinned to a different cluster segment via their own `nodeSelector` or `affinity`, and all registered to the same Hub. The Hub distributes session requests across them, and each Node provisions browser Pods that inherit its own placement constraints.
 
 ```
-                         ┌─────────────────────────────────┐
+                         ┌─────────────────────────────────-┐
                          │             Hub                  │
-                         └──────┬──────────────┬───────────┘
+                         └──────┬──────────────┬───────────-┘
                                 │              │
-               ┌────────────────▼──┐      ┌───▼────────────────┐
+               ┌────────────────▼──┐      ┌───-▼────────────────┐
                │ NodeKubernetes    │      │ NodeKubernetes      │
                │ nodeSelector:     │      │ nodeSelector:       │
                │   zone=us-west    │      │   zone=us-east      │
-               └────────┬──────────┘      └────────┬───────────┘
+               └────────┬──────────┘      └────────-┬───────────┘
                         │ inherits spec             │ inherits spec
-              ┌─────────▼──────────┐    ┌──────────▼──────────┐
+              ┌─────────▼──────────┐    ┌──────────-▼──────────┐
               │  browser Pod       │    │  browser Pod         │
               │  (us-west, same    │    │  (us-east, same      │
               │   tolerations...)  │    │   tolerations...)    │
-              └────────────────────┘    └─────────────────────┘
+              └────────────────────┘    └─────────────────────-┘
 ```
 
 Teams can keep multiple Dynamic Nodes on standby — lightweight processes consuming minimal resources — and let the browser Pods scale horizontally on demand within each segment. This approach fits naturally into cluster autoscaler workflows: idle Nodes hold their spot in the cluster; browser Jobs drive the actual compute scaling.
@@ -229,7 +229,7 @@ The Node validates the event, enriches it with `nodeId`, `nodeUri`, and `timesta
 
 ### Multi-language client support
 
-Firing events is surfaced directly on the driver instance in **all five official language bindings**. No manual HTTP wiring needed — the driver knows the session ID and Grid URL:
+Firing events is surfaced directly on the driver instance in **all five official language bindings** (required binding version 4.41.0+ also). No manual HTTP wiring needed — the driver knows the session ID and Grid URL:
 
 ```python
 # Python
@@ -329,7 +329,7 @@ Set `SE_UPLOAD_FAILURE_SESSION_ONLY=true` and the uploader will **skip cloud upl
 A session is treated as failed under two conditions:
 
 1. **Custom failure event fired** — your test framework calls `driver.fire_session_event("test:failed", ...)` during the session. The sidecar matches the event type against a configurable list of failure patterns.
-2. **Abnormal close** — the session timed out or crashed without a clean `session-closed` event.
+2. **Abnormal close reason** — the `session-closed` event is received but carries a `reason` other than `QUIT_COMMAND`. Currently, that means `TIMEOUT` (session exceeded the configured timeout) or `NODE_REMOVED` (the node was forcibly removed from the Grid). A clean `driver.quit()` sends `QUIT_COMMAND` and is never treated as a failure.
 
 The failure event type matching is controlled by `SE_UPLOAD_FAILURE_SESSION_EVENTS` (default: `:failed,:failure`). The match is a substring check on the event type, so the default catches `test:failed`, `suite:failed`, `step:failure`, etc. You can extend the list for your own conventions: