diff --git a/source/_integrations/anthropic.markdown b/source/_integrations/anthropic.markdown
index ec06105b0c6..de15e626a9b 100644
--- a/source/_integrations/anthropic.markdown
+++ b/source/_integrations/anthropic.markdown
@@ -49,29 +49,23 @@ The Anthropic API key is used to authenticate requests to the Anthropic API. To
 {% include integrations/config_flow.md %}
 
 {% include integrations/option_flow.md %}
+
 {% configuration_basic %}
 Instructions:
   description: Instructions for the AI on how it should respond to your requests. It is written using [Home Assistant Templating](/docs/configuration/templating/).
-
 Control Home Assistant:
   description: If the model is allowed to interact with Home Assistant. It can only control or provide information about entities that are [exposed](/voice_control/voice_remote_expose_devices/) to it.
-
 Recommended settings:
   description: If enabled, the recommended model and settings are chosen.
-
 {% endconfiguration_basic %}
 
 If you choose not to use the recommended settings, you can configure the following options:
 
 {% configuration_basic %}
-
 Model:
   description: The model that will complete your prompt. See [models](https://docs.anthropic.com/en/docs/about-claude/models#model-names) for additional details and options.
-
 Maximum Tokens to Return in Response:
   description: The maximum number of tokens to generate before stopping. Note that our models may stop _before_ reaching this maximum. This parameter only specifies the absolute maximum number of tokens to generate. Different models have different maximum values for this parameter. See [models](https://docs.anthropic.com/en/docs/models-overview) for details.
-
 Temperature:
   description: Amount of randomness injected into the response. Use `temperature` closer to `0.0` for analytical / multiple choice, and closer to `1.0` for creative and generative tasks. Note that even with `temperature` of `0.0`, the results will not be fully deterministic.
-
 {% endconfiguration_basic %}
diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown
index 466ea28004e..447b11597d9 100644
--- a/source/_integrations/cast.markdown
+++ b/source/_integrations/cast.markdown
@@ -21,14 +21,14 @@ ha_integration_type: integration
 Support for mDNS discovery in your local network is mandatory for automatic discovery. Make sure that your router has this feature enabled. If mDNS does not work in your network, the IP addresses of the Cast devices can be manually entered in the configuration as mentioned below.
 
 {% include integrations/option_flow.md %}
+
 {% configuration_basic %}
 Known hosts:
   description: "A comma-separated list of hostnames or IP-addresses of cast devices, use if mDNS discovery is not working"
 Allowed UUIDs:
   description: A comma-separated list of UUIDs of Cast devices to add to Home Assistant. **Use only if you don't want to add all available devices.** The device won't be added until discovered through either mDNS or if it's included in the list of known hosts. In order to find the UUID for your device use a mDNS browser or advanced users can use the following Python command (adjust friendly names as required) - `python3 -c "import pychromecast; print(pychromecast.get_listed_chromecasts(friendly_names=['Living Room TV', 'Bedroom TV', 'Office Chromecast']))"`. This option is only visible if advanced mode is enabled in your user profile.
 Ignore CEC:
-  description: A comma-separated list of Chromecasts that should ignore CEC data for determining the
-        active input. [See the upstream documentation for more information](https://github.com/home-assistant-libs/pychromecast#ignoring-cec-data). This option is only visible if advanced mode is enabled in your user profile.
+  description: A comma-separated list of Chromecasts that should ignore CEC data for determining the active input. [See the upstream documentation for more information](https://github.com/home-assistant-libs/pychromecast#ignoring-cec-data). This option is only visible if advanced mode is enabled in your user profile.
 {% endconfiguration_basic %}
 
 ## Home Assistant Cast
diff --git a/source/_integrations/fyta.markdown b/source/_integrations/fyta.markdown
index daca58a61d9..e04feb4946c 100644
--- a/source/_integrations/fyta.markdown
+++ b/source/_integrations/fyta.markdown
@@ -32,9 +32,9 @@ To setup the integration you need the following information:
 
 {% configuration_basic %}
 Email:
-    description: "The email address used to access the FYTA account."
+  description: "The email address used to access the FYTA account."
 Password:
-    description: "The password used to access the FYTA account."
+  description: "The password used to access the FYTA account."
 {% endconfiguration_basic %}
 
 ## Configuration options
diff --git a/source/_integrations/google_generative_ai_conversation.markdown b/source/_integrations/google_generative_ai_conversation.markdown
index 1a16625436b..386373001ef 100644
--- a/source/_integrations/google_generative_ai_conversation.markdown
+++ b/source/_integrations/google_generative_ai_conversation.markdown
@@ -45,41 +45,31 @@ On the same page, you can see your plan: *free of charge* if the associated Goog
 Comparison of the plans is available [at this pricing page](https://ai.google.dev/pricing). The major differences include: the free of charge plan is rate limited, free prompts/responses are used for product improvement, and the free plan is not available in all [regions](https://ai.google.dev/gemini-api/docs/available-regions).
 
 {% include integrations/option_flow.md %}
-{% configuration_basic %}
 
+{% configuration_basic %}
 Instructions:
   description: Instructions for the AI on how it should respond to your requests. It is written using [Home Assistant Templating](/docs/configuration/templating/).
-
 Control Home Assistant:
   description: If the model is allowed to interact with Home Assistant. It can only control or provide information about entities that are [exposed](/voice_control/voice_remote_expose_devices/) to it.
-
 Recommended settings:
   description: If enabled, the recommended model and settings are chosen.
-
 {% endconfiguration_basic %}
 
 If you choose to not use the recommended settings, you can configure the following options:
 
 {% configuration_basic %}
-
 Model:
   description: Model used to generate response.
-
 Temperature:
   description: Creativity allowed in the responses. Higher values produce a more random and varied response. A temperature of zero will be deterministic.
-
 Top P:
   description: Probability threshold for top-p sampling.
-
 Top K:
   description: Number of top-scored tokens to consider during generation.
-
 Maximum Tokens to Return in Response:
   description: The maximum number of words or "tokens" that the AI model should generate.
-
 Safety settings:
   description: Thresholds for different [harmful categories](https://ai.google.dev/gemini-api/docs/safety-settings).
-
 {% endconfiguration_basic %}
 
 ## Talking to Super Mario
diff --git a/source/_integrations/habitica.markdown b/source/_integrations/habitica.markdown
index 808d9ce9e3f..c56f3bf373a 100644
--- a/source/_integrations/habitica.markdown
+++ b/source/_integrations/habitica.markdown
@@ -55,9 +55,9 @@ The Habitica integration lets you automate task management, such as creating to-
 
 {% configuration_basic %}
 "Email or username":
-    description: "Email or username (case-sensitive) to connect Home Assistant to your Habitica account"
+  description: "Email or username (case-sensitive) to connect Home Assistant to your Habitica account"
 Password:
-    description: "Password for the account to connect Home Assistant to Habitica"
+  description: "Password for the account to connect Home Assistant to Habitica"
 {% endconfiguration_basic %}
 
 ### Advanced configuration
@@ -66,11 +66,11 @@ If you choose "**Login to other instances**" you will be presented the following
 
 {% configuration_basic %}
 "User ID":
-    description: "User ID of your Habitica account (*see [prerequisites](#prerequisites-for-habitica-integration)*)"
+  description: "User ID of your Habitica account (*see [prerequisites](#prerequisites-for-habitica-integration)*)"
 API Token:
-    description: "API Token of the Habitica account (*see [prerequisites](#prerequisites-for-habitica-integration)*)"
+  description: "API Token of the Habitica account (*see [prerequisites](#prerequisites-for-habitica-integration)*)"
 URL:
-    description: "URL of the Habitica installation to connect to. Defaults to `https://habitica.com` (*see [prerequisites](#prerequisites-for-habitica-integration)*)"
+  description: "URL of the Habitica installation to connect to. Defaults to `https://habitica.com` (*see [prerequisites](#prerequisites-for-habitica-integration)*)"
 Verify SSL certificate:
   description: Enable SSL certificate verification for secure connections. Disable only if connecting to a Habitica instance using a self-signed certificate
 {% endconfiguration_basic %}
diff --git a/source/_integrations/homewizard.markdown b/source/_integrations/homewizard.markdown
index 3684e9088bd..4b352f1467b 100644
--- a/source/_integrations/homewizard.markdown
+++ b/source/_integrations/homewizard.markdown
@@ -44,7 +44,7 @@ You have to enable the local API to allow Home Assistant to communicate with you
 
 {% configuration_basic %}
 IP address:
-    description: "The IP address of your device. You can find it in your router."
+  description: "The IP address of your device. You can find it in your router."
 {% endconfiguration_basic %}
 
 ## Sensors
diff --git a/source/_integrations/husqvarna_automower.markdown b/source/_integrations/husqvarna_automower.markdown
index 01bf7e7ff38..e3734694f06 100644
--- a/source/_integrations/husqvarna_automower.markdown
+++ b/source/_integrations/husqvarna_automower.markdown
@@ -78,11 +78,11 @@ Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://hom
 
 {% configuration_basic %}
 Name:
-    description: "Enter the name for the provided credentials. You can choose your favorite name."
+  description: "Enter the name for the provided credentials. You can choose your favorite name."
 OAuth Client ID:
-    description: "Enter the Application key from your Husqvarna developer application."
+  description: "Enter the Application key from your Husqvarna developer application."
 OAuth Client Secret:
-    description: "Enter the Application secret from your Husqvarna developer application."
+  description: "Enter the Application secret from your Husqvarna developer application."
 {% endconfiguration_basic %}
 
 ## Troubleshooting
diff --git a/source/_integrations/idasen_desk.markdown b/source/_integrations/idasen_desk.markdown
index 1df4b341e0f..bfe0eeddfdb 100644
--- a/source/_integrations/idasen_desk.markdown
+++ b/source/_integrations/idasen_desk.markdown
@@ -45,8 +45,6 @@ This integration provides two buttons to connect and disconnect to/from the desk
 ## Sensors
 
 {% configuration_basic %}
-
 Height:
   description: The current height of the desk, in meters.
-
 {% endconfiguration_basic %}
diff --git a/source/_integrations/imap.markdown b/source/_integrations/imap.markdown
index 513b32f376d..41352d3be0c 100644
--- a/source/_integrations/imap.markdown
+++ b/source/_integrations/imap.markdown
@@ -130,7 +130,6 @@ initial:
   description: Returns `True` if this is the initial event for the last message received. When a message within the search scope is removed and the last message received has not been changed, then an `imap_content` event is generated and the `initial` property is set to `False`. Note that if no `Message-ID` header was set on the triggering email, the `initial` property will always be set to `True`.
 uid:
   description: Latest `uid` of the message.
-
 {% endconfiguration_basic %}
 
 The `event_type` for the custom event should be set to `imap_content`. The configuration below shows how you can use the event data in a template `sensor`.
diff --git a/source/_integrations/integration.markdown b/source/_integrations/integration.markdown
index 1c40f629d0a..d097abdaa4c 100644
--- a/source/_integrations/integration.markdown
+++ b/source/_integrations/integration.markdown
@@ -40,8 +40,7 @@ Metric prefix:
 Integration time:
   description: SI unit of time to integrate over.
 Max sub-interval:
-  description: Applies time-based integration if the source did not change for this duration. This implies that at least every `max sub-interval`, the integral is updated. If you don't want time-based updates, enter 0.
-
+  description: Applies time-based integration if the source did not change for this duration. This implies that at least every `max sub-interval`, the integral is updated. If you don't want time-based updates, enter `0`.
 {% endconfiguration_basic %}
 
 
diff --git a/source/_integrations/ista_ecotrend.markdown b/source/_integrations/ista_ecotrend.markdown
index 3bf3065aed8..f980b667e26 100644
--- a/source/_integrations/ista_ecotrend.markdown
+++ b/source/_integrations/ista_ecotrend.markdown
@@ -43,10 +43,10 @@ The integration currently supports only the German EcoTrend service.
 {% include integrations/config_flow.md %}
 
 {% configuration_basic %}
-"Email":
-    description: "Enter the email address associated with your ista EcoTrend account to connect it to Home Assistant."
+Email:
+  description: "Enter the email address associated with your ista EcoTrend account to connect it to Home Assistant."
 Password:
-    description: "Enter the password for your ista EcoTrend account to enable the connection with Home Assistant."
+  description: "Enter the password for your ista EcoTrend account to enable the connection with Home Assistant."
 {% endconfiguration_basic %}
 
 ## Sensors
diff --git a/source/_integrations/min_max.markdown b/source/_integrations/min_max.markdown
index 43a830e968b..08a35b72ddf 100644
--- a/source/_integrations/min_max.markdown
+++ b/source/_integrations/min_max.markdown
@@ -24,6 +24,7 @@ The sensor provided by this integration will always show you the lowest/highest/
 If the source sensor provides an unknown state, it will be ignored in the calculation except for sum where it will set the state to unknown. If the unit of measurement of the sensors differs, the Min/Max sensor will go to an error state where the value is `UNKNOWN` and unit of measurement is `ERR`.
 
 {% include integrations/config_flow.md %}
+
 {% configuration_basic %}
 Name:
   description: The name the sensor should have. You can change it again later.
diff --git a/source/_integrations/netgear.markdown b/source/_integrations/netgear.markdown
index d494f47f273..0393458b150 100644
--- a/source/_integrations/netgear.markdown
+++ b/source/_integrations/netgear.markdown
@@ -29,12 +29,14 @@ Attached devices are only tracked on NETGEAR devices set to the router mode, oth
 {% include integrations/config_flow.md %}
 
 {% include integrations/option_flow.md %}
+
 {% configuration_basic %}
 Consider_home:
   description: "The consider home time is the number of seconds to wait till marking someone as not home after not being seen. This parameter is most useful for households with Apple iOS devices that go into sleep mode while still at home to conserve battery life. iPhones will occasionally drop off the network and then re-appear. This option helps prevent false alarms in presence detection."
 {% endconfiguration_basic %}
 
 ## Router entities
+
 The NETGEAR router will have the following entities.
 
 Note that not all routers support all features, if a router does not support a feature, the corresponding entity will have the unavailable status even when the entity is disabled.
diff --git a/source/_integrations/nuki.markdown b/source/_integrations/nuki.markdown
index 6fe076ddda8..9c3169df3a7 100644
--- a/source/_integrations/nuki.markdown
+++ b/source/_integrations/nuki.markdown
@@ -29,14 +29,14 @@ For faster updates, the callback function of the Nuki bridge can be used. This r
 {% include integrations/config_flow.md %}
 
 {% configuration_basic %}
-  Host:
-    description: Hostname or IP address of your Nuki bridge, e.g., `192.168.1.25`.
-  Port:
-    description: Port of the Nuki bridge HTTP API, default is `8080`.
-  Token:
-    description: Token to authenticate against the Nuki bridge HTTP API.
-  Use an encrypted token for authentication:
-    description: Use an encrypted token for API calls to the bridge. This should only be deactivated if you experience issues with the API (authentication, etc). The default is `True`.
+Host:
+  description: Hostname or IP address of your Nuki bridge, e.g., `192.168.1.25`.
+Port:
+  description: Port of the Nuki bridge HTTP API, default is `8080`.
+Token:
+  description: Token to authenticate against the Nuki bridge HTTP API.
+Use an encrypted token for authentication:
+  description: Use an encrypted token for API calls to the bridge. This should only be deactivated if you experience issues with the API (authentication, etc). The default is `True`.
 {% endconfiguration_basic %}
 
 ## Actions
diff --git a/source/_integrations/ollama.markdown b/source/_integrations/ollama.markdown
index ca226ba54fe..d2ad23caf3b 100644
--- a/source/_integrations/ollama.markdown
+++ b/source/_integrations/ollama.markdown
@@ -32,27 +32,22 @@ This integration requires an external Ollama server, which is available for macO
 {% include integrations/config_flow.md %}
 
 {% include integrations/option_flow.md %}
+
 {% configuration_basic %}
 URL:
   description: The URL of the external Ollama server, such as `http://localhost:11434`.
-  
 Model:
   description: Name of the [Ollama model](https://ollama.com/library) to use, such as `mistral` or `llama2:13b`. Models will be automatically downloaded during setup.
-
 Instructions:
   description: Instructions for the AI on how it should respond to your requests. It is written using [Home Assistant Templating](/docs/configuration/templating/).
-
 Control Home Assistant:
   description: If the model is allowed to interact with Home Assistant. It can only control or provide information about entities that are [exposed](/voice_control/voice_remote_expose_devices/) to it. This feature is considered experimental and see [Controlling Home Assistant](#controlling-home-assistant) below for details on model limitations.
-
 Context window size:
   description: "The context window size is the number of tokens the model can take as input. Home Assistant defaults to 8k, which is larger than the default value in Ollama Server (2k), and you may adjust it based on the maximum context size of the specific model used. A larger value will better support larger homes with more entities, and smaller values may lower Ollama server RAM usage."
 Max history messages:
   description: Maximum number of messages to keep for each conversation (0 = no limit). Limiting this value will cause older messages in a conversation to be dropped.
-
 Keep alive:
   description: Duration in seconds for the Ollama host to keep the model in memory after receiving a message (-1 = no limit, 0 = no retention). Default value is -1.
-
 {% endconfiguration_basic %}
 
 ## Controlling Home Assistant
diff --git a/source/_integrations/openai_conversation.markdown b/source/_integrations/openai_conversation.markdown
index 870f232c947..977e8458891 100644
--- a/source/_integrations/openai_conversation.markdown
+++ b/source/_integrations/openai_conversation.markdown
@@ -43,34 +43,27 @@ The OpenAI key is used to authenticate requests to the OpenAI API. To generate a
 - Visit the [API Keys page](https://platform.openai.com/account/api-keys) to retrieve the API key you'll use to configure the integration.
 
 {% include integrations/option_flow.md %}
+
 {% configuration_basic %}
 Instructions:
   description: Instructions for the AI on how it should respond to your requests. It is written using [Home Assistant Templating](/docs/configuration/templating/).
-
 Control Home Assistant:
   description: If the model is allowed to interact with Home Assistant. It can only control or provide information about entities that are [exposed](/voice_control/voice_remote_expose_devices/) to it.
-
 Recommended settings:
   description: If enabled, the recommended model and settings are chosen.
-
 {% endconfiguration_basic %}
 
 If you choose to not use the recommended settings, you can configure the following options:
 
 {% configuration_basic %}
-
 Model:
   description: The GPT language model is used for text generation. You can find more details on the available models in the [OpenAI GPT-3.5 Turbo Documentation](https://platform.openai.com/docs/models/gpt-3-5-turbo), [OpenAI GPT-4 Turbo and GPT-4 Documentation](https://platform.openai.com/docs/models/gpt-4-turbo-and-gpt-4), or [GPT-4o Documentation](https://platform.openai.com/docs/models/gpt-4o). The default is "gpt-4o".
-
 Maximum Tokens to Return in Response:
   description: The maximum number of words or "tokens" that the AI model should generate in its completion of the prompt. For more information, see the [OpenAI Completion Documentation](https://platform.openai.com/docs/guides/completion/introduction).
-
 Temperature:
   description: A value that determines the level of creativity and risk-taking the model should use when generating text. A higher temperature means the model is more likely to generate unexpected results, while a lower temperature results in more deterministic results. See the [OpenAI Completion Documentation](https://platform.openai.com/docs/guides/completion/introduction) for more information.
-
 Top P:
   description: An alternative to temperature, top_p determines the proportion of the most likely word choices the model should consider when generating text. A higher top_p means the model will only consider the most likely words, while a lower top_p means a wider range of words, including less likely ones, will be considered. For more information, see the [OpenAI Completion API Reference](https://platform.openai.com/docs/api-reference/completions/create#completions/create-top_p).
-
 {% endconfiguration_basic %}
 
 ## Talking to Super Mario over the phone
diff --git a/source/_integrations/pegel_online.markdown b/source/_integrations/pegel_online.markdown
index 112c4cf0791..9eba1c356d8 100644
--- a/source/_integrations/pegel_online.markdown
+++ b/source/_integrations/pegel_online.markdown
@@ -30,18 +30,18 @@ Select the area, where you want to search for available water measuring stations
 
 {% configuration_basic %}
 Latitude:
-    description: "The latitude of the center of the search area (_automatically filled by the location picker_)."
+  description: "The latitude of the center of the search area (_automatically filled by the location picker_)."
 Longitude:
-    description: "The longitude of the center of the search area (_automatically filled by the location picker_)."
+  description: "The longitude of the center of the search area (_automatically filled by the location picker_)."
 Radius:
-    description: "Search radius (_in km_)"
+  description: "Search radius (_in km_)"
 {% endconfiguration_basic %}
 
 ### Step 2 - Station selection
 
 {% configuration_basic %}
 Station:
-    description: "Select the measurement station you want to add."
+  description: "Select the measurement station you want to add."
 {% endconfiguration_basic %}
 
 ## Sensors
diff --git a/source/_integrations/rainbird.markdown b/source/_integrations/rainbird.markdown
index cd059a09bfd..80c893ab763 100644
--- a/source/_integrations/rainbird.markdown
+++ b/source/_integrations/rainbird.markdown
@@ -48,10 +48,9 @@ irrigations schedules on a calendar.
 
 {% configuration_basic %}
 Host:
-    description: "The IP address of your Rain Bird device. You can find the IP address under the
-    device in the Rain Bird app under **Controller Settings** -> **Network Info**."
+  description: "The IP address of your Rain Bird device. You can find the IP address under the device in the Rain Bird app under **Controller Settings** -> **Network Info**."
 Password:
-    description: "The password used to authenticate the Rain Bird device."
+  description: "The password used to authenticate the Rain Bird device."
 {% endconfiguration_basic %}
 
 ## Configuration options
diff --git a/source/_integrations/renault.markdown b/source/_integrations/renault.markdown
index 7cc7fd0e2d0..38fe25bdeb9 100644
--- a/source/_integrations/renault.markdown
+++ b/source/_integrations/renault.markdown
@@ -38,13 +38,13 @@ This integration provides the following platforms:
 
 {% configuration_basic %}
 Locale:
-    description: "The country code (e.g., 'fr_FR', 'en_GB') used to connect to the Renault servers. This should match your MyRenault account's locale setting."
+  description: "The country code (e.g., `fr_FR`, `en_GB`) used to connect to the Renault servers. This should match your MyRenault account's locale setting."
 Username:
-    description: "The username used to connect to the Renault servers."
+  description: "The username used to connect to the Renault servers."
 Password:
-    description: "The password used to connect to the Renault servers."
+  description: "The password used to connect to the Renault servers."
 Kamereon account id:
-    description: "The Kamereon account ID that your vehicles are assigned to. If there is only one account available it will be automatically selected."
+  description: "The Kamereon account ID that your vehicles are assigned to. If there is only one account available it will be automatically selected."
 {% endconfiguration_basic %}
 
 All vehicles linked to the account should then get added as devices, with sensors added as linked entity.
diff --git a/source/_integrations/solarlog.markdown b/source/_integrations/solarlog.markdown
index 075813c32aa..d8253c522be 100644
--- a/source/_integrations/solarlog.markdown
+++ b/source/_integrations/solarlog.markdown
@@ -42,13 +42,13 @@ To setup the integration you need the following information:
 
 {% configuration_basic %}
 Name:
-    description: "The name for your Solar-Log device in Home Assistant. This will also be uses as prefix for the entity names."
+  description: "The name for your Solar-Log device in Home Assistant. This will also be uses as prefix for the entity names."
 Host:
-    description: "The URL or IP address of your Solar-Log."
+  description: "The URL or IP address of your Solar-Log."
 User password available:
-    description: "Check the box, if you have the password for the Solar-Log user to securely access [all data](#additional-data)."
+  description: "Check the box, if you have the password for the Solar-Log user to securely access [all data](#additional-data)."
 Password:
-    description: "Password for the Solar-Log user. Will only be asked for in a second step, if in the first step the checkbox has been selected."
+  description: "Password for the Solar-Log user. Will only be asked for in a second step, if in the first step the checkbox has been selected."
 {% endconfiguration_basic %}
 
 ## Configuration options
diff --git a/source/_integrations/swiss_public_transport.markdown b/source/_integrations/swiss_public_transport.markdown
index b27495ab4ef..cc76f08ff13 100644
--- a/source/_integrations/swiss_public_transport.markdown
+++ b/source/_integrations/swiss_public_transport.markdown
@@ -21,11 +21,11 @@ The [Swiss public transport API](https://transport.opendata.ch/) only allows 100
 
 {% configuration_basic %}
 Start station:
-    description: "The departure station for the start of the connection (e.g., 'Zürich HB')"
+  description: "The departure station for the start of the connection (e.g., `Zürich HB`)"
 End station:
-    description: "The arrival station for the end of the connection (e.g., 'Geneva')"
+  description: "The arrival station for the end of the connection (e.g., `Geneva`)"
 Via stations:
-    description: "List of up to 5 via stations (e.g., 'Bern, Lausanne')"
+  description: "List of up to 5 via stations (e.g., `Bern`, `Lausanne`)"
 {% endconfiguration_basic %}
 
 Use the [Stationboard](https://transport.opendata.ch/examples/stationboard.html) to find exact station names.
diff --git a/source/_integrations/switch_as_x.markdown b/source/_integrations/switch_as_x.markdown
index cb8a0e6cd8f..269ff53526f 100644
--- a/source/_integrations/switch_as_x.markdown
+++ b/source/_integrations/switch_as_x.markdown
@@ -39,6 +39,7 @@ Using the **Change device type of a switch** helper integration, you can convert
 entity types that best matches your use case.
 
 {% include integrations/config_flow.md name="Switch as X" %}
+
 {% configuration_basic %}
 Switch entity:
   description: The switch entity you want to convert into something else.
diff --git a/source/_integrations/threshold.markdown b/source/_integrations/threshold.markdown
index 28d12c9a9b0..7eaa7364b1f 100644
--- a/source/_integrations/threshold.markdown
+++ b/source/_integrations/threshold.markdown
@@ -20,6 +20,7 @@ The threshold integration observes the state of another sensor. If the value is
 If the sensor is configured with no hysteresis and the sensor value is equal to the threshold, the sensor is turned off since it is not upper or lower with respect to the threshold.
 
 {% include integrations/config_flow.md %}
+
 {% configuration_basic %}
 Name:
   description: The name the sensor should have. You can change it again later.
diff --git a/source/_integrations/tod.markdown b/source/_integrations/tod.markdown
index 57e458ef019..29ea8a9cb03 100644
--- a/source/_integrations/tod.markdown
+++ b/source/_integrations/tod.markdown
@@ -17,6 +17,7 @@ ha_integration_type: helper
 The Times of the Day integration provides a binary sensor that gets its values by checking if the current time is within defined time ranges.
 
 {% include integrations/config_flow.md %}
+
 {% configuration_basic %}
 Name:
   description: The name the binary sensor should have. This can be changed later.
diff --git a/source/_integrations/traccar_server.markdown b/source/_integrations/traccar_server.markdown
index 83c70210b64..a1428ef7cd1 100644
--- a/source/_integrations/traccar_server.markdown
+++ b/source/_integrations/traccar_server.markdown
@@ -40,7 +40,6 @@ Examples:
 All events will also have the following data:
 
 {% configuration_basic %}
-
 Device ID:
   description: (`device_traccar_id`) This will be the device ID that the event is related to.
 Device name:
@@ -51,7 +50,6 @@ Server time:
   description: (`serverTime`) This will be the time the event was received by the Traccar Server.
 Attributes:
   description: (`attributes`) This will be a dictionary of attributes related to the event.
-
 {% endconfiguration_basic %}
 
 {% details "Example" %}
diff --git a/source/_integrations/trend.markdown b/source/_integrations/trend.markdown
index dca6ef56421..9a942f0c78b 100644
--- a/source/_integrations/trend.markdown
+++ b/source/_integrations/trend.markdown
@@ -24,6 +24,7 @@ Thus it can take some time to show an accurate state. It can be useful
 as part of automations, where you want to base an action on a trend.
 
 {% include integrations/config_flow.md %}
+
 {% configuration_basic %}
 Name:
   description: The name the sensor should have. You can change it again later.
diff --git a/source/_integrations/version.markdown b/source/_integrations/version.markdown
index 2c150d61478..2a9b4782141 100644
--- a/source/_integrations/version.markdown
+++ b/source/_integrations/version.markdown
@@ -27,21 +27,16 @@ The **Version** {% term integration %} can display the current Home Assistant Co
 With this {% term integration %} you can select various sources to get a version from.
 
 {% configuration_basic %}
-  "Local installation":
-    description: This will get the version you are currently running.
-
-  "Home Assistant Versions":
-    description: This will use the same source that are used by the Supervisor to check for updates based on the channel and image you choose.
-
-  "Home Assistant Website":
-    description: This will check the website you are reading this on to find the latest version.
-
-  "Docker Hub":
-    description: This will check the latest tag published to Docker Hub based on the channel and image you choose.
-
-  "Python Package Index (PyPI)":
-    description: This will check PyPI for the latest published package.
-
+Local installation:
+  description: This will get the version you are currently running.
+Home Assistant Versions:
+  description: This will use the same source that are used by the Supervisor to check for updates based on the channel and image you choose.
+Home Assistant Website:
+  description: This will check the website you are reading this on to find the latest version.
+Docker Hub:
+  description: This will check the latest tag published to Docker Hub based on the channel and image you choose.
+Python Package Index (PyPI):
+  description: This will check PyPI for the latest published package.
 {% endconfiguration_basic %}
 
 ## Entities
diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown
index 740023293eb..0126f3b30fa 100644
--- a/source/_integrations/xiaomi_miio.markdown
+++ b/source/_integrations/xiaomi_miio.markdown
@@ -1695,7 +1695,6 @@ Enter remote control mode, make one move, stop, and exit remote control mode.
 ### Sensors
 
 {% configuration_basic %}
-
 DnD Start*:
   description: The timestamp when the next DnD (Do not disturb) period will start
 DnD End*:
@@ -1732,7 +1731,6 @@ Water Box Attached**:
   description: If the watter box is attached
 Water Shortage\*\*:
   description: If the water box is low on water
-
 {% endconfiguration_basic %}
 
 {% note %}