chore: various markdown warnings resolved (#30657)

Co-authored-by: Evan Rusackas <evan@preset.io>

docs/docs/installation/architecture.mdx

@@ -14,6 +14,7 @@ This page is meant to give new administrators an understanding of Superset's com
 ## Components
 
 A Superset installation is made up of these components:
+
 1. The Superset application itself
 2. A metadata database
 3. A caching layer (optional, but necessary for some features)
@@ -22,6 +23,7 @@ A Superset installation is made up of these components:
 ### Optional components and associated features
 
 The optional components above are necessary to enable these features:
+
 - [Alerts and Reports](/docs/configuration/alerts-reports)
 - [Caching](/docs/configuration/cache)
 - [Async Queries](/docs/configuration/async-queries-celery/)
@@ -36,6 +38,7 @@ Here are further details on each component.
 ### The Superset Application
 
 This is the core application. Superset operates like this:
+
 - A user visits a chart or dashboard
 - That triggers a SQL query to the data warehouse holding the underlying dataset
 - The resulting data is served up in a data visualization
@@ -52,6 +55,7 @@ For production, a properly-configured, managed, standalone database is recommend
 ### Caching Layer
 
 The caching layer serves two main functions:
+
 - Store the results of queries to your data warehouse so that when a chart is loaded twice, it pulls from the cache the second time, speeding up the application and reducing load on your data warehouse.
 - Act as a message broker for the worker, enabling the Alerts & Reports, async queries, and thumbnail caching features.
 

docs/docs/installation/docker-builds.mdx

@@ -59,14 +59,13 @@ Here are the build presets that are exposed through the `supersetbot docker` uti
   this specific SHA, which could be from a `master` merge, or release.
 - `websocket-latest`: The WebSocket image for use in a Superset cluster.
 
-
-
 For insights or modifications to the build matrix and tagging conventions,
 check the [supersetbot docker](https://github.com/apache-superset/supersetbot)
 subcommand and the [docker.yml](https://github.com/apache/superset/blob/master/.github/workflows/docker.yml)
 GitHub action.
 
 ## Key ARGs in Dockerfile
+
 - `BUILD_TRANSLATIONS`: whether to build the translations into the image. For the
   frontend build this tells webpack to strip out all locales other than `en` from
   the `moment-timezone` library. For the backendthis skips compiling the

docs/docs/installation/kubernetes.mdx

@@ -157,6 +157,7 @@ instead of hard-coding them in your bootstrap script, as seen below.
 :::
 
 The following example installs the drivers for BigQuery and Elasticsearch, allowing you to connect to these data sources within your Superset setup:
+
 ```yaml
 bootstrapScript: |
   #!/bin/bash