diff --git a/timescaledb/how-to-guides/configuration/telemetry.md b/timescaledb/how-to-guides/configuration/telemetry.md
index 14bbd594b0..be12877802 100644
--- a/timescaledb/how-to-guides/configuration/telemetry.md
+++ b/timescaledb/how-to-guides/configuration/telemetry.md
@@ -8,8 +8,7 @@ appropriately seeded random number generators.
 
 This is an example of the JSON data file that is sent to our servers about a
 specific deployment:
-
-```javascript
+```json
 {
 	"db_uuid": "26917841-2fc0-48fd-b096-ba19b3fda98f",
 	"license": {
@@ -83,48 +82,48 @@ If you disable telemetry, the version checking functionality is also disabled.
 <procedure>
 
 ### Disabling telemetry
+
 1.  Open your PostgreSQL configuration file, and locate
-		the `timescaledb.telemetry_level` parameter. See our
-		[PostgreSQL configuration file][postgres-config] instructions for locating
-		and opening the file.
-1. 	Change the parameter setting to `off`:
-		```txt
-	  timescaledb.telemetry_level=off
-	 	```
-1. 	Reload the configuration file:
-		```bash
-		pg_ctl
-		```
-1. 	Alternatively, you can use this command at the `psql` prompt, as the root
-		user:
-	  ```sql
-		ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=off
-	  ```
-	 	This command disables telemetry for the specified system, database, or user.
+    the `timescaledb.telemetry_level` parameter. See our
+    [PostgreSQL configuration file][postgres-config] instructions for locating
+    and opening the file.
+1.  Change the parameter setting to `off`:
+    ```yaml
+    timescaledb.telemetry_level=off
+    ```
+1.  Reload the configuration file:
+    ```bash
+    pg_ctl
+    ```
+1.  Alternatively, you can use this command at the `psql` prompt, as the root
+    user:
+    ```sql
+    ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=off
+    ```
+    This command disables telemetry for the specified system, database, or user.
 
 </procedure>
 
 <procedure>
 
 ### Enabling telemetry
-1. 	Open your PostgreSQL configuration file, and locate
-		the `timescaledb.telemetry_level` parameter. See our
-		[PostgreSQL configuration file][postgres-config] instructions for locating
-		and opening the file.
-1. 	Change the parameter setting to `off`:
-		```txt
-		timescaledb.telemetry_level=basic
-		```
-1. 	Reload the configuration file:
-		```bash
-		pg_ctl
-		```
-1. 	Alternatively, you can use this command at the `psql` prompt, as the root
-		user:
-		```sql
-		ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=basic
-		```
-		This command enables telemetry for the specified system, database, or user.
+
+1. Open your PostgreSQL configuration file, and locate the 'timescaledb.telemetry_level' 
+	parameter. See our [PostgreSQL configuration file][postgres-config] instructions for locating and opening the file.
+
+1. Change the parameter setting to 'off':
+	```yaml
+	timescaledb.telemetry_level=basic
+	```
+1. Reload the configuration file:
+	```bash
+	pg_ctl
+	```
+1. Alternatively, you can use this command at the `psql` prompt, as the root user:
+	```sql
+	ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=basic
+	```
+	This command enables telemetry for the specified system, database, or user.
 
 </procedure>
 
diff --git a/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md b/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md
index e9090c5cbf..e1c0b5938b 100644
--- a/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md
+++ b/timescaledb/how-to-guides/multinode-timescaledb/multinode-maintenance.md
@@ -5,11 +5,11 @@ access node keeps a log of distributed transactions so that nodes that haven't
 completed their part of the distributed transaction can complete it later when
 they become available. This transaction log requires regular cleanup to remove
 transactions that have completed, and complete those that haven't.
-
 We highly recommended that you configure the access node to run a maintenance
 job that regularly cleans up any unfinished distributed transactions.
 
 The custom maintenance job can be run as a user-defined action. For example:
+
 ```sql
 CREATE OR REPLACE PROCEDURE data_node_maintenance(job_id int, config jsonb)
 LANGUAGE SQL AS