fix more code blocks

Author: Blargian

docs/en/guides/developer/understanding-query-execution-with-the-analyzer.md

@@ -275,7 +275,7 @@ EXPLAIN PIPELINE graph=1 WITH
 SELECT type, min(timestamp) AS minimum_date, max(timestamp) AS maximum_date, count(*) /total_rows * 100 AS percentage FROM session_events GROUP BY type FORMAT TSV;
 ```
 
-```
+```response
 digraph
 {
  rankdir="LR";

docs/en/guides/sre/keeper/index.md

@@ -238,7 +238,7 @@ Node count: 4
 
 - `srst`: Reset server statistics. The command will affect the result of `srvr`, `mntr` and `stat`.
 
-```
+```response
 Server stats reset.
 ```
 
@@ -314,7 +314,7 @@ log_dir_size: 3875
 
 - `isro`: Tests if server is running in read-only mode. The server will respond with `ro` if in read-only mode or `rw` if not in read-only mode.
 
-```
+```response
 rw
 ```
 
@@ -886,7 +886,8 @@ This guide provides simple and minimal settings to configure ClickHouse Keeper w
     ```
 
     On `chnode2`:
-    ```
+6. 
+    ```sql
     SELECT *
     FROM db1.table1
     ```
@@ -1218,8 +1219,10 @@ Database must be `Atomic`, if upgrading from a previous version, the
 :::
 
 To check:
+
 For example,
-```
+
+```sql
 SELECT name, engine FROM system.databases WHERE name = 'db_uuid';
 ```
 
@@ -1256,7 +1259,7 @@ Alternatively, you can send a `reconfig` query through any ZooKeeper-compatible
 
 A virtual node `/keeper/config` contains last committed cluster configuration in the following format:
 
-```
+```text
 server.id = server_host:server_port[;server_type][;server_priority]
 server.id2 = ...
 ...
@@ -1269,7 +1272,7 @@ server.id2 = ...
 
 Example:
 
-```
+```sql
 :) get /keeper/config
 server.1=zoo1:9234;participant;1
 server.2=zoo2:9234;participant;1

docs/en/managing-data/core-concepts/partitions.md

@@ -216,7 +216,8 @@ The output above shows:
 
 ② Granule pruning: Row 19 to 24 of the EXPLAIN output above indicate that ClickHouse then uses the [primary index](/docs/en/optimize/sparse-primary-indexes) (created over the `town`-field) of the data part identified in step ① to  
 further reduce the number of granules (that contain rows potentially also matching the query's `town` filter) from 11 to 1. This is also reflected in the ClickHouse-client output that we printed further above for the query run:
-```
+
+```response
 ... Elapsed: 0.006 sec. Processed 8.19 thousand rows, 57.34 KB (1.36 million rows/s., 9.49 MB/s.)
 Peak memory usage: 2.73 MiB.
 ```

docs/en/use-cases/observability/introduction.md

@@ -71,7 +71,7 @@ We currently recommend ClickHouse for storing two types of observability data:
 
 - **Logs** - Logs are time-stamped records of events occurring within a system, capturing detailed information about various aspects of software operations. The data in logs is typically unstructured or semi-structured and can include error messages, user activity logs, system changes, and other events. Logs are crucial for troubleshooting, anomaly detection, and understanding the specific events leading up to issues within the system.
 
-```
+```response
 54.36.149.41 - - [22/Jan/2019:03:56:14 +0330] "GET
 /filter/27|13%20%D9%85%DA%AF%D8%A7%D9%BE%DB%8C%DA%A9%D8%B3%D9%84,27|%DA%A9%D9%85%D8%AA%D8%B1%20%D8%A7%D8%B2%205%20%D9%85%DA%AF%D8%A7%D9%BE%DB%8C%DA%A9%D8%B3%D9%84,p53 HTTP/1.1" 200 30577 "-" "Mozilla/5.0 (compatible; AhrefsBot/6.1; +http://ahrefs.com/robot/)" "-"
 ```