chore: cleanup documentation (#29552)

superset/db_engine_specs/README.md

@@ -175,6 +175,7 @@ FROM
 GROUP BY
   UPPER(country_of_origin)
 ```
+
 ### `time_groupby_inline = False`
 
 In theory this attribute should be used to omit time filters from the self-joins. When the attribute is false the time attribute will be present in the subquery used to compute limited series, eg:
@@ -415,13 +416,13 @@ DB engine specs should implement a class method called `get_function_names` that
 
 Superset does a good job in keeping credentials secure. When you add a database with a password, for example:
 
-```
+```text
 postgresql://admin:password123@db.example.org:5432/db
 ```
 
 The password is sent over the network only when the database is created. When you edit the database later, Superset will return this as the SQLAlchemy URI:
 
-```
+```text
 postgresql://admin:XXXXXXXXXX@db.example.org:5432/db
 ```
 
@@ -429,7 +430,7 @@ The password will be masked in the API response; it's not just masked in the bro
 
 When the database is edited, the Superset backend is smart enough to replace the masked password with the actual password, unless the password has changed. That is, if you change the database in the URI from `db` to `db2` the SQLAlchemy URI will be stored in the backend as:
 
-```
+```text
 postgresql://admin:password123@db.example.org:5432/db2
 ```