diff --git a/source/_integrations/alarm_control_panel.mqtt.markdown b/source/_integrations/alarm_control_panel.mqtt.markdown
index 91b2b4fa4842..64cad9af0606 100644
--- a/source/_integrations/alarm_control_panel.mqtt.markdown
+++ b/source/_integrations/alarm_control_panel.mqtt.markdown
@@ -11,7 +11,7 @@ related:
     title: Configuration file
 ---
 
-The `mqtt` alarm panel {% term integration %} enables the possibility to control MQTT capable alarm panels. The Alarm icon will change state after receiving a new state from `state_topic`. If these messages are published with *RETAIN* flag, the MQTT alarm panel will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state will be `unknown`.
+The **MQTT Alarm control panel** {% term integration %} enables the possibility to control MQTT capable alarm panels. The Alarm icon will change state after receiving a new state from `state_topic`. If these messages are published with *RETAIN* flag, the MQTT alarm panel will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state will be `unknown`.
 
 The {% term integration %} will accept the following states from your Alarm Panel (in lower case):
 
diff --git a/source/_integrations/binary_sensor.mqtt.markdown b/source/_integrations/binary_sensor.mqtt.markdown
index d663d8f523b7..8f031dc3c48e 100644
--- a/source/_integrations/binary_sensor.mqtt.markdown
+++ b/source/_integrations/binary_sensor.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` binary sensor platform uses an MQTT message received to set the binary sensor's state to `on`, `off` or `unknown`.
+The **MQTT binary sensor** {% term integration %} uses an MQTT message received to set the binary sensor's state to `on`, `off` or `unknown`.
 
 The state will be updated only after a new message is published on `state_topic` matching `payload_on`, `payload_off` or `None`. If these messages are published with the `retain` flag set,
 the binary sensor will receive an instant state update after subscription and Home Assistant will display the correct state on startup.
diff --git a/source/_integrations/blackbird.markdown b/source/_integrations/blackbird.markdown
index e107a6609e64..28c243ea3db9 100644
--- a/source/_integrations/blackbird.markdown
+++ b/source/_integrations/blackbird.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `blackbird` platform allows you to control [Monoprice Blackbird Matrix Switch](https://www.monoprice.com/product?p_id=21819) (8x8) using a serial or IP connection, this integration does not support the 4x4 matrix switch.
+The **Monoprice Blackbird Matrix Switch** {% term integration %} allows you to control [Monoprice Blackbird Matrix Switch](https://www.monoprice.com/product?p_id=21819) (8x8) using a serial or IP connection, this integration does not support the 4x4 matrix switch.
 
 To add a Blackbird 8x8 device to your installation, add the following to your {% term "`configuration.yaml`" %} file.
 {% include integrations/restart_ha_after_config_inclusion.md %}
diff --git a/source/_integrations/button.mqtt.markdown b/source/_integrations/button.mqtt.markdown
index ac2e5c03aa69..97daa233483b 100644
--- a/source/_integrations/button.mqtt.markdown
+++ b/source/_integrations/button.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` button platform lets you send an MQTT message when the button is pressed in the frontend or the button press action is called. This can be used to expose some service of a remote device, for example reboot.
+The **MQTT button** {% term integration %} lets you send an MQTT message when the button is pressed in the frontend or the button press action is called. This can be used to expose some service of a remote device, for example reboot.
 
 To use an MQTT button in your installation, [add a MQTT device as a subentry](/integrations/mqtt/#configuration), or add the following to your {% term "`configuration.yaml`" %} file.
 {% include integrations/restart_ha_after_config_inclusion.md %}
diff --git a/source/_integrations/camera.mqtt.markdown b/source/_integrations/camera.mqtt.markdown
index d37693ca28b7..bcdd5a5afe18 100644
--- a/source/_integrations/camera.mqtt.markdown
+++ b/source/_integrations/camera.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated. Messages received on `topic` should contain the full contents of an image file, for example, a JPEG image, without any additional encoding or metadata.
+The **MQTT camera** {% term integration %} allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated. Messages received on `topic` should contain the full contents of an image file, for example, a JPEG image, without any additional encoding or metadata.
 
 This can be used with an application or a service capable of sending images through MQTT.
 
diff --git a/source/_integrations/ccm15.markdown b/source/_integrations/ccm15.markdown
index 62197b917787..fe13050e6c65 100644
--- a/source/_integrations/ccm15.markdown
+++ b/source/_integrations/ccm15.markdown
@@ -15,7 +15,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The CCM15 integration allows you to integrate [Midea CCM15](https://mbt.midea.com/hvac-goods/midea-products-category/vrfs/vrf-controller/central-controller-ccm-15) devices in Home Assistant.
+The **CCM15** {% term integration %} allows you to integrate [Midea CCM15](https://mbt.midea.com/hvac-goods/midea-products-category/vrfs/vrf-controller/central-controller-ccm-15) devices in Home Assistant.
 
 There is currently support for the following device types within Home Assistant:
 
diff --git a/source/_integrations/climate.mqtt.markdown b/source/_integrations/climate.mqtt.markdown
index cbbcbaecdeb6..f73499242726 100644
--- a/source/_integrations/climate.mqtt.markdown
+++ b/source/_integrations/climate.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Local Polling
 ha_domain: mqtt
 ---
 
-The `mqtt` climate platform lets you control your MQTT enabled HVAC devices.
+The **MQTT climate** {% term integration %} lets you control your MQTT enabled HVAC devices.
 
 ## Configuration
 
diff --git a/source/_integrations/cover.mqtt.markdown b/source/_integrations/cover.mqtt.markdown
index 6a1fa0a5b74f..f50052d25ab0 100644
--- a/source/_integrations/cover.mqtt.markdown
+++ b/source/_integrations/cover.mqtt.markdown
@@ -8,7 +8,7 @@ ha_release: 0.18
 ha_domain: mqtt
 ---
 
-The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a roller shutter or a garage door).
+The **MQTT cover** {% term integration %} allows you to control an MQTT cover (such as blinds, a roller shutter or a garage door).
 
 ## Configuration
 
diff --git a/source/_integrations/device_tracker.mqtt.markdown b/source/_integrations/device_tracker.mqtt.markdown
index b078c2e59b28..42df73bb17ce 100644
--- a/source/_integrations/device_tracker.mqtt.markdown
+++ b/source/_integrations/device_tracker.mqtt.markdown
@@ -12,7 +12,7 @@ related:
 ---
 
 
-The `mqtt` device tracker {% term integration %} allows you to define new device_trackers through [manual YAML configuration](#yaml-configuration) in {% term "`configuration.yaml`" %} and also to automatically discover device_trackers [using the MQTT Discovery protocol](#using-the-discovery-protocol).
+The **MQTT device tracker** {% term integration %} allows you to define new device_trackers through [manual YAML configuration](#yaml-configuration) in {% term "`configuration.yaml`" %} and also to automatically discover device_trackers [using the MQTT Discovery protocol](#using-the-discovery-protocol).
 
 ## Configuration
 
diff --git a/source/_integrations/device_trigger.mqtt.markdown b/source/_integrations/device_trigger.mqtt.markdown
index 174807d66fa3..f088655cd411 100644
--- a/source/_integrations/device_trigger.mqtt.markdown
+++ b/source/_integrations/device_trigger.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` device trigger platform uses an MQTT message payload to generate device trigger events.
+The **MQTT Device trigger** {% term integration %} uses an MQTT message payload to generate device trigger events.
 
 An MQTT device trigger is a better option than a [binary sensor](/integrations/binary_sensor.mqtt/) for buttons, remote controls etc.
 
diff --git a/source/_integrations/event.mqtt.markdown b/source/_integrations/event.mqtt.markdown
index 8b50821aa99a..1af569f5d546 100644
--- a/source/_integrations/event.mqtt.markdown
+++ b/source/_integrations/event.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` event platform allows you to process event info from an MQTT message. Events are signals that are emitted when something happens, for example, when a user presses a physical button like a doorbell or when a button on a remote control is pressed. With the event some event attributes can be sent to become available as an attribute on the entity. MQTT events are stateless. For example, a doorbell does not have a state like being "on" or "off" but instead is momentarily pressed.
+The **MQTT Event** {% term integration %} allows you to process event info from an MQTT message. Events are signals that are emitted when something happens, for example, when a user presses a physical button like a doorbell or when a button on a remote control is pressed. With the event some event attributes can be sent to become available as an attribute on the entity. MQTT events are stateless. For example, a doorbell does not have a state like being "on" or "off" but instead is momentarily pressed.
 
 ## Configuration
 
diff --git a/source/_integrations/fan.mqtt.markdown b/source/_integrations/fan.mqtt.markdown
index c5e53238ec55..2c72f122da55 100644
--- a/source/_integrations/fan.mqtt.markdown
+++ b/source/_integrations/fan.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` fan platform lets you control your MQTT enabled fans.
+The **MQTT Fan** {% term integration %} lets you control your MQTT enabled fans.
 
 ## Configuration
 
diff --git a/source/_integrations/flux_led.markdown b/source/_integrations/flux_led.markdown
index c8a5a8f14880..c1db5cb74118 100644
--- a/source/_integrations/flux_led.markdown
+++ b/source/_integrations/flux_led.markdown
@@ -26,7 +26,7 @@ ha_dhcp: true
 ha_integration_type: integration
 ---
 
-The Magic Home {% term integration %} supports several brands of switches, bulbs, and controllers that use the same protocol. Chances are high that your bulb or controller (eg. WiFi LED CONTROLLER) will work with this integration if you can control the device with the Magic Home app or the Surp Life app.
+The **Magic Home** {% term integration %} supports several brands of switches, bulbs, and controllers that use the same protocol. Chances are high that your bulb or controller (eg. WiFi LED CONTROLLER) will work with this integration if you can control the device with the Magic Home app or the Surp Life app.
 
 This integration will provide local control over your LED lights/strips and can be configured to auto-scan your network for controllers or for you to manually configure individual lights by their IP address.
 
diff --git a/source/_integrations/humidifier.mqtt.markdown b/source/_integrations/humidifier.mqtt.markdown
index 3bd4a5502b76..5e50b83889a1 100644
--- a/source/_integrations/humidifier.mqtt.markdown
+++ b/source/_integrations/humidifier.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` humidifier platform lets you control your MQTT enabled humidifiers.
+The **MQTT Humidifier** {% term integration %} lets you control your MQTT enabled humidifiers.
 
 ## Configuration
 
diff --git a/source/_integrations/image.mqtt.markdown b/source/_integrations/image.mqtt.markdown
index 5f85402109a2..054995976601 100644
--- a/source/_integrations/image.mqtt.markdown
+++ b/source/_integrations/image.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` image platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as an image.
+The **MQTT Image** {% term integration %} allows you to integrate the content of an image file sent through MQTT into Home Assistant as an image.
 The `image` platform is a simplified version of the `camera` platform that only accepts images.
 Every time a message under the `image_topic` in the configuration is received, the image displayed in Home Assistant will also be updated. Messages received on `image_topic` should contain the full contents of an image file, for example, a JPEG image, without any additional encoding or metadata.
 
diff --git a/source/_integrations/lawn_mower.mqtt.markdown b/source/_integrations/lawn_mower.mqtt.markdown
index e1eaeb2103d3..d67fbc991620 100644
--- a/source/_integrations/lawn_mower.mqtt.markdown
+++ b/source/_integrations/lawn_mower.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` `lawn_mower` platform allows controlling a lawn mower over MQTT.
+The **MQTT lawn mower** {% term integration %} allows controlling a lawn mower over MQTT.
 
 ## Configuration
 
diff --git a/source/_integrations/light.mqtt.markdown b/source/_integrations/light.mqtt.markdown
index eafb99a0f183..0cf04ec7128c 100644
--- a/source/_integrations/light.mqtt.markdown
+++ b/source/_integrations/light.mqtt.markdown
@@ -8,7 +8,7 @@ ha_release: 0.8
 ha_domain: mqtt
 ---
 
-The `mqtt` light platform lets you control your MQTT enabled lights through one of the supported message schemas, `default`, `json` or `template`.
+The **MQTT Light** {% term integration %} lets you control your MQTT enabled lights through one of the supported message schemas, `default`, `json` or `template`.
 
 ## Comparison of light MQTT schemas
 
diff --git a/source/_integrations/lock.mqtt.markdown b/source/_integrations/lock.mqtt.markdown
index be3a938212ed..debfceb806b6 100644
--- a/source/_integrations/lock.mqtt.markdown
+++ b/source/_integrations/lock.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` lock platform lets you control your MQTT enabled locks.
+The **MQTT Lock** {% term integration %} lets you control your MQTT enabled locks.
 
 ## Configuration
 
diff --git a/source/_integrations/madvr.markdown b/source/_integrations/madvr.markdown
index f3efe2626850..6c46c2d39905 100644
--- a/source/_integrations/madvr.markdown
+++ b/source/_integrations/madvr.markdown
@@ -19,7 +19,7 @@ ha_platforms:
 ha_integration_type: device
 ---
 
-The madVR Envy allows for the automation and control of [madVR Envy devices](https://madvrenvy.com).
+The **madVR Envy** {% term integration %} allows for the automation and control of [madVR Envy devices](https://madvrenvy.com).
 
 ## Supported Devices
 
diff --git a/source/_integrations/manual.markdown b/source/_integrations/manual.markdown
index e8f98d91aee7..eda1e6661787 100644
--- a/source/_integrations/manual.markdown
+++ b/source/_integrations/manual.markdown
@@ -16,7 +16,7 @@ related:
     title: Configuration file
 ---
 
-The `manual` alarm control panel {% term integration %} enables you to create an alarm system in Home Assistant.
+The **Manual Alarm control panel** {% term integration %} enables you to create an alarm system in Home Assistant.
 
 ## Configuration
 
diff --git a/source/_integrations/manual_mqtt.markdown b/source/_integrations/manual_mqtt.markdown
index 1c9e884aeca6..d05e4e359eb3 100644
--- a/source/_integrations/manual_mqtt.markdown
+++ b/source/_integrations/manual_mqtt.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mqtt` {% term integration %} extends the [manual alarm](/integrations/manual) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
+The **MQTT** {% term integration %} extends the [manual alarm](/integrations/manual) by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
 
 It's essentially the opposite of the [MQTT Alarm Panel](/integrations/alarm_control_panel.mqtt/) which allows Home Assistant to observe an existing, fully-featured alarm where all of the alarm logic is embedded in that physical device.
 
diff --git a/source/_integrations/marytts.markdown b/source/_integrations/marytts.markdown
index e475bc99cb66..12b3778e7eed 100644
--- a/source/_integrations/marytts.markdown
+++ b/source/_integrations/marytts.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `marytts` text-to-speech {% term integration %} uses [MaryTTS](https://marytts.github.io/) text-to-speech engine to read a text with natural sounding voices.
+The **MaryTTS** {% term integration %} uses [MaryTTS](https://marytts.github.io/) text-to-speech engine to read a text with natural sounding voices.
 
 ## Configuration
 
diff --git a/source/_integrations/mastodon.markdown b/source/_integrations/mastodon.markdown
index 2b1a2240a99c..985570e5c165 100644
--- a/source/_integrations/mastodon.markdown
+++ b/source/_integrations/mastodon.markdown
@@ -19,7 +19,7 @@ ha_config_flow: true
 ha_quality_scale: bronze
 ---
 
-The `mastodon` platform uses [Mastodon](https://joinmastodon.org/) to post status updates and get account statistics.
+The **Mastodon** {% term integration %} uses [Mastodon](https://joinmastodon.org/) to post status updates and get account statistics.
 
 ### Setup
 
diff --git a/source/_integrations/matter.markdown b/source/_integrations/matter.markdown
index 65203e67f56d..e9a1d18b8a65 100644
--- a/source/_integrations/matter.markdown
+++ b/source/_integrations/matter.markdown
@@ -55,7 +55,7 @@ related:
 ha_zeroconf: true
 ---
 
-The Matter {% term integration %} allows you to control Matter devices on your local Wi-Fi or {% term Thread %} network.
+The **Matter** {% term integration %} allows you to control Matter devices on your local Wi-Fi or {% term Thread %} network.
 
 For communicating with Matter devices, the Home Assistant integration runs its own "Matter controller" as add-on. This Matter Server add-on runs the controller software as a separate process and connects your Matter network (called Fabric in technical terms) and Home Assistant. The Home Assistant Matter integration connects to this server via a WebSocket connection.
 
diff --git a/source/_integrations/meater.markdown b/source/_integrations/meater.markdown
index 834de4d1bbfb..df6149c580d6 100644
--- a/source/_integrations/meater.markdown
+++ b/source/_integrations/meater.markdown
@@ -16,7 +16,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Meater Smart Meat Thermometer {% term integration %} allows for communicating with the [Meater Temperature Probe](https://meater.com/) from Apption Labs.
+The **Meater** {% term integration %} allows for communicating with the [Meater Temperature Probe](https://meater.com/) from Apption Labs.
 
 {% include integrations/config_flow.md %}
 
diff --git a/source/_integrations/media_extractor.markdown b/source/_integrations/media_extractor.markdown
index 53ed8459bb04..76f4f12c622c 100644
--- a/source/_integrations/media_extractor.markdown
+++ b/source/_integrations/media_extractor.markdown
@@ -16,7 +16,7 @@ related:
 ha_config_flow: true
 ---
 
-The Media extractor {% term integration %} gets a stream URL and sends it to a media player entity. This integration can extract entity specific streams if configured accordingly.
+The **Media extractor** {% term integration %} gets a stream URL and sends it to a media player entity. This integration can extract entity specific streams if configured accordingly.
 
 {% note %}
 Media extractor doesn't transcode streams, it just tries to find a stream that matches the requested query.
diff --git a/source/_integrations/media_source.markdown b/source/_integrations/media_source.markdown
index aac6bee840ba..8484679dbb40 100644
--- a/source/_integrations/media_source.markdown
+++ b/source/_integrations/media_source.markdown
@@ -11,7 +11,7 @@ ha_quality_scale: internal
 ha_integration_type: system
 ---
 
-The Media source {% term integration %} platform allows integrations to expose media for
+The **Media source** {% term integration %} platform allows integrations to expose media for
 use inside Home Assistant through the Media Browser panel or through supported
 media players like Google Cast.
 
diff --git a/source/_integrations/mediaroom.markdown b/source/_integrations/mediaroom.markdown
index f4028df6034d..03fd83dcfd49 100644
--- a/source/_integrations/mediaroom.markdown
+++ b/source/_integrations/mediaroom.markdown
@@ -17,7 +17,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mediaroom` {% term integration %} allows you to control a [Mediaroom](https://en.wikipedia.org/wiki/Ericsson_Mediaroom) Set-Top Box (STB) from Home Assistant.
+The **Mediaroom** {% term integration %} allows you to control a [Mediaroom](https://en.wikipedia.org/wiki/Ericsson_Mediaroom) Set-Top Box (STB) from Home Assistant.
 
 To add a Mediaroom STB to your installation, add the following to your {% term "`configuration.yaml`" %} file.
 {% include integrations/restart_ha_after_config_inclusion.md %}
diff --git a/source/_integrations/melcloud.markdown b/source/_integrations/melcloud.markdown
index 952a7fd76059..e2e65051ff6c 100644
--- a/source/_integrations/melcloud.markdown
+++ b/source/_integrations/melcloud.markdown
@@ -17,7 +17,7 @@ ha_codeowners:
   - '@erwindouna'
 ---
 
-The `melcloud` integration integrates Mitsubishi Electric's [MELCloud](https://www.melcloud.com/) enabled devices into Home Assistant.
+The **MELCloud** {% term integration %} integrates Mitsubishi Electric's [MELCloud](https://www.melcloud.com/) enabled devices into Home Assistant.
 
 ## Device support
 
diff --git a/source/_integrations/melissa.markdown b/source/_integrations/melissa.markdown
index ddd1bf43d45f..5ac7f9b1108c 100644
--- a/source/_integrations/melissa.markdown
+++ b/source/_integrations/melissa.markdown
@@ -18,7 +18,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `melissa` {% term integration %} is the main integration to connect to a [Melissa Climate](https://seemelissa.com/) A/C control.
+The **Melissa** {% term integration %} is the main integration to connect to a [Melissa Climate](https://seemelissa.com/) A/C control.
 
 There is currently support for the following device types within Home Assistant:
 
diff --git a/source/_integrations/melnor.markdown b/source/_integrations/melnor.markdown
index 58503f1873a2..0ca183b463b9 100644
--- a/source/_integrations/melnor.markdown
+++ b/source/_integrations/melnor.markdown
@@ -19,7 +19,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Melnor Bluetooth integration allows you to control your Melnor Bluetooth watering valves.
+The **Melnor Bluetooth** {% term integration %} allows you to control your Melnor Bluetooth watering valves.
 The devices are set up through Bluetooth and don't need any additional bridge or gateway.
 
 1-zone, 2-zone, and 4-zone valves are supported.
diff --git a/source/_integrations/message_bird.markdown b/source/_integrations/message_bird.markdown
index 77a7fddbdaa6..2de5b64479ba 100644
--- a/source/_integrations/message_bird.markdown
+++ b/source/_integrations/message_bird.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `MessageBird` notification {% term integration %} sends notifications as SMS messages using [MessageBird](https://www.messagebird.com/) to your mobile phone.
+The **MessageBird** {% term integration %} sends notifications as SMS messages using [MessageBird](https://www.messagebird.com/) to your mobile phone.
 
 ## Setup
 
diff --git a/source/_integrations/met.markdown b/source/_integrations/met.markdown
index d35c93a6f28a..82ccf40ad595 100644
--- a/source/_integrations/met.markdown
+++ b/source/_integrations/met.markdown
@@ -14,6 +14,6 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `met` platform uses the [Met.no](https://met.no/) web service as a source for meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK.
+The **Meteorologisk institutt (Met.no)** {% term integration %} uses the [Met.no](https://met.no/) web service as a source for meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK.
 
 {% include integrations/config_flow.md %}
diff --git a/source/_integrations/met_eireann.markdown b/source/_integrations/met_eireann.markdown
index be09a9f00f4a..ef1eac073b61 100644
--- a/source/_integrations/met_eireann.markdown
+++ b/source/_integrations/met_eireann.markdown
@@ -14,7 +14,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Met Éireann {% term integration %} uses the [Met Éireann](https://met.ie) (The Irish Meteorological Service) Public Weather Forecast API to provide current and forecasted weather data for a given location. This integration is in no way affiliated with or endorsed by Met Éireann.
+The **Met Éireann** {% term integration %} uses the [Met Éireann](https://met.ie) (The Irish Meteorological Service) Public Weather Forecast API to provide current and forecasted weather data for a given location. This integration is in no way affiliated with or endorsed by Met Éireann.
 
 {% note %}
 The Met Éireann API will only provide data for Ireland, the UK and a small part of northern France. For specific coverage, please see the Notes on API document available [here](https://data.gov.ie/dataset/met-eireann-forecast-api/resource/027da6d5-d819-48d1-9b16-331dba169bd1).
diff --git a/source/_integrations/meteo_france.markdown b/source/_integrations/meteo_france.markdown
index 2849cfdc55e8..d2324f288679 100644
--- a/source/_integrations/meteo_france.markdown
+++ b/source/_integrations/meteo_france.markdown
@@ -18,7 +18,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `meteo_france` integration uses the meteorological data from [Météo-France](http://www.meteofrance.com/) to provide weather forecast for any location in the world with a focus on France. One or more locations can be set via the front end or via the configuration file.
+The **Météo-France** {% term integration %} uses the meteorological data from [Météo-France](http://www.meteofrance.com/) to provide weather forecast for any location in the world with a focus on France. One or more locations can be set via the front end or via the configuration file.
 
 The integration support the following platforms within Home Assistant:
 
diff --git a/source/_integrations/meteoalarm.markdown b/source/_integrations/meteoalarm.markdown
index 44ac62f0acc0..3df30690b50f 100644
--- a/source/_integrations/meteoalarm.markdown
+++ b/source/_integrations/meteoalarm.markdown
@@ -14,7 +14,7 @@ ha_integration_type: integration
 ha_quality_scale: legacy
 ---
 
-The `MeteoAlarm` platform allows one to watch for weather alerts in Europe from [MeteoAlarm](https://www.meteoalarm.org) (EUMETNET). To use this binary sensor, you need the country and the province name from  [MeteoAlarm](https://feeds.meteoalarm.org). Please note that it is crucial to write the country name exactly as it appears in the URL starting with https://feeds.meteoalarm.org/feeds/meteoalarm-legacy-atom-, including any hyphens used in the name. Failure to do so may result in errors or incorrect data.
+The **MeteoAlarm** {% term integration %} allows one to watch for weather alerts in Europe from [MeteoAlarm](https://www.meteoalarm.org) (EUMETNET). To use this binary sensor, you need the country and the province name from  [MeteoAlarm](https://feeds.meteoalarm.org). Please note that it is crucial to write the country name exactly as it appears in the URL starting with https://feeds.meteoalarm.org/feeds/meteoalarm-legacy-atom-, including any hyphens used in the name. Failure to do so may result in errors or incorrect data.
 
 The name of the province can be found using the [MeteoAlarm EMMA_ID Region explorer tool](https://saratoga-weather.org/meteoalarm-map/)
 
diff --git a/source/_integrations/meteoclimatic.markdown b/source/_integrations/meteoclimatic.markdown
index a4964a65a3cb..67b263d6f9f2 100644
--- a/source/_integrations/meteoclimatic.markdown
+++ b/source/_integrations/meteoclimatic.markdown
@@ -16,7 +16,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Meteoclimatic {% term integration %} uses the [Meteoclimatic](https://www.meteoclimatic.net/) web service as a source for meteorological data for your location. The location is based on the Meteoclimatic station code (e.g., `ESCAT4300000043206B`) and the weather data reported is based on the capabilities of each station.
+The **Meteoclimatic** {% term integration %} uses the [Meteoclimatic](https://www.meteoclimatic.net/) web service as a source for meteorological data for your location. The location is based on the Meteoclimatic station code (e.g., `ESCAT4300000043206B`) and the weather data reported is based on the capabilities of each station.
 
 There is currently support for the following platforms within Home Assistant:
 
diff --git a/source/_integrations/microbees.markdown b/source/_integrations/microbees.markdown
index efb91c3d1b54..70a8c6df13e6 100644
--- a/source/_integrations/microbees.markdown
+++ b/source/_integrations/microbees.markdown
@@ -27,7 +27,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The microbees {% term integration %} allows you to control your [microBees devices](https://www.microbees.com/) such as plugs and wall switches.
+The **microBees** {% term integration %} allows you to control your [microBees devices](https://www.microbees.com/) such as plugs and wall switches.
 To use this integration you need OAuth2 Client ID and Client Secret and your user credentials.
 
 To retrieve the OAuth2 Client ID and Client Secret go to [microBees Developer Dashboard](https://developers.microbees.com/dashboard), login with your microBees account and [create a new app](https://developers.microbees.com/dashboard/?p=wizard), choose a Label for your App, select WebApplication and input https://my.home-assistant.io as Website URL.
diff --git a/source/_integrations/microsoft.markdown b/source/_integrations/microsoft.markdown
index ba31a7d0f4d2..7e347dcc6cff 100644
--- a/source/_integrations/microsoft.markdown
+++ b/source/_integrations/microsoft.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `microsoft` text-to-speech {% term integration %} uses the [TTS engine of the Microsoft Speech Service](https://learn.microsoft.com/azure/cognitive-services/speech-service/text-to-speech) to read a text with natural sounding voices. This integration uses an API that is part of the Cognitive Services offering and is known as the Microsoft Speech API. For this integration to work, you need a free API key. You can use your [Azure subscription](https://azure.microsoft.com) to create an [Azure Speech resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesSpeechServices).
+The **Microsoft text-to-speech** {% term integration %} uses the [TTS engine of the Microsoft Speech Service](https://learn.microsoft.com/azure/cognitive-services/speech-service/text-to-speech) to read a text with natural sounding voices. This integration uses an API that is part of the Cognitive Services offering and is known as the Microsoft Speech API. For this integration to work, you need a free API key. You can use your [Azure subscription](https://azure.microsoft.com) to create an [Azure Speech resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesSpeechServices).
 
 ## Configuration
 
diff --git a/source/_integrations/microsoft_face.markdown b/source/_integrations/microsoft_face.markdown
index 15342f3f23b4..ddc46c7a93fa 100644
--- a/source/_integrations/microsoft_face.markdown
+++ b/source/_integrations/microsoft_face.markdown
@@ -10,7 +10,7 @@ ha_integration_type: integration
 ha_quality_scale: legacy
 ---
 
-The `microsoft_face` {% term integration %} is the main integration for Microsoft
+The **Microsoft Face** {% term integration %} is the main integration for Microsoft
 Azure Cognitive service
 [Face](https://azure.microsoft.com/products/cognitive-services/vision-services).
 All data are stored in your own private instance in the Azure cloud.
diff --git a/source/_integrations/microsoft_face_detect.markdown b/source/_integrations/microsoft_face_detect.markdown
index 0d01c6c428d0..616030a2a426 100644
--- a/source/_integrations/microsoft_face_detect.markdown
+++ b/source/_integrations/microsoft_face_detect.markdown
@@ -13,7 +13,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `microsoft_face_detect` image processing {% term integration %} allows you to use the
+The **Microsoft Face Detect** {% term integration %} allows you to use the
 [Microsoft Face Identify](https://azure.microsoft.com/products/cognitive-services/)
 API through Home Assistant. This platform enables you to detect face on camera
 and fire an event with attributes.
diff --git a/source/_integrations/microsoft_face_identify.markdown b/source/_integrations/microsoft_face_identify.markdown
index 2df47729fb7d..e48580b956c8 100644
--- a/source/_integrations/microsoft_face_identify.markdown
+++ b/source/_integrations/microsoft_face_identify.markdown
@@ -13,7 +13,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `microsoft_face_identify` image processing {% term integration %} lets you use
+The **Microsoft Face Identify** {% term integration %} lets you use
 [Microsoft Face identify](https://azure.microsoft.com/products/cognitive-services/)
 API through Home Assistant. This platform allow you do identify persons on
 camera and fire an event with attributes.
diff --git a/source/_integrations/miele.markdown b/source/_integrations/miele.markdown
index 6b9c10dec761..fbc6324ce0d2 100644
--- a/source/_integrations/miele.markdown
+++ b/source/_integrations/miele.markdown
@@ -34,7 +34,7 @@ ha_zeroconf: true
 ha_quality_scale: platinum
 ---
 
-The Miele {% term integrations %} allows users to integrate their home appliances using the [official 3rd party API](https://www.miele.com/developer).
+The **Miele** {% term integration %} allows users to integrate their home appliances using the [official 3rd party API](https://www.miele.com/developer).
 
 Miele is known as a manufacturer of premium appliances for cooking, laundry care, and floor care.
 
diff --git a/source/_integrations/mikrotik.markdown b/source/_integrations/mikrotik.markdown
index fbdeeecdfecc..2651bc31b4d9 100644
--- a/source/_integrations/mikrotik.markdown
+++ b/source/_integrations/mikrotik.markdown
@@ -15,7 +15,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `mikrotik` platform offers presence detection by looking at connected devices to a [MikroTik RouterOS](https://mikrotik.com) based router.
+The **MikroTik** {% term integration %} offers presence detection by looking at connected devices to a [MikroTik RouterOS](https://mikrotik.com) based router.
 
 There is currently support for the following device types within Home Assistant:
 
diff --git a/source/_integrations/min_max.markdown b/source/_integrations/min_max.markdown
index 4ffbb76e3379..35eaba9cbdee 100644
--- a/source/_integrations/min_max.markdown
+++ b/source/_integrations/min_max.markdown
@@ -17,7 +17,7 @@ ha_platforms:
 ha_integration_type: helper
 ---
 
-The Min/Max {% term integration %} consumes the state from other sensors to determine the minimum, maximum, latest (last), mean, median, range and sum of the collected states.
+The **Min/Max** {% term integration %} consumes the state from other sensors to determine the minimum, maximum, latest (last), mean, median, range and sum of the collected states.
 
 The sensor provided by this integration will always show you the lowest/highest/latest value which was received from all monitored sensors. If you have spikes in your values, it's recommended to filter/equalize your values with a [statistics sensor](/integrations/statistics) first.
 
diff --git a/source/_integrations/mjpeg.markdown b/source/_integrations/mjpeg.markdown
index 72f4ec5447b6..d125f01ba61f 100644
--- a/source/_integrations/mjpeg.markdown
+++ b/source/_integrations/mjpeg.markdown
@@ -12,7 +12,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The MJPEG IP Camera integration allows you to integrate IP cameras which are
+The **MJPEG IP Camera** {% term integration %} allows you to integrate IP cameras which are
 capable to stream their video with MJPEG (Motion JPEG) into Home Assistant.
 
 ## Prerequisites
diff --git a/source/_integrations/mobile_app.markdown b/source/_integrations/mobile_app.markdown
index 59f901c76908..bcf0da2e0a90 100644
--- a/source/_integrations/mobile_app.markdown
+++ b/source/_integrations/mobile_app.markdown
@@ -18,7 +18,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Mobile App {% term integration %} allows Home Assistant mobile apps to easily integrate with Home Assistant.
+The **Mobile App** {% term integration %} allows Home Assistant mobile apps to easily integrate with Home Assistant.
 
 If you are planning to use a mobile application that integrates with Home Assistant, we recommend that you keep this integration enabled.
 
diff --git a/source/_integrations/mochad.markdown b/source/_integrations/mochad.markdown
index 44ec9d17b1e8..9beac5968f53 100644
--- a/source/_integrations/mochad.markdown
+++ b/source/_integrations/mochad.markdown
@@ -18,7 +18,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mochad` {% term integration %} is the main integration to integrate all X10 platforms being controlled by [mochad](https://sourceforge.net/projects/mochad/). Besides this integration you will have to setup your X10 devices separately.
+The **Mochad** {% term integration %} is the main integration to integrate all X10 platforms being controlled by [mochad](https://sourceforge.net/projects/mochad/). Besides this integration you will have to setup your X10 devices separately.
 
 There is currently support for the following device types within Home Assistant:
 
diff --git a/source/_integrations/moehlenhoff_alpha2.markdown b/source/_integrations/moehlenhoff_alpha2.markdown
index 47c78c97ef85..7ee0216aa7d2 100644
--- a/source/_integrations/moehlenhoff_alpha2.markdown
+++ b/source/_integrations/moehlenhoff_alpha2.markdown
@@ -17,7 +17,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Möhlenhoff Alpha 2 integration allows you to control a [Möhlenhoff Alpha 2](https://dev.moehlenhoff.de/en/products/room-by-room-control/oem-alpha-2-system)
+The **Möhlenhoff Alpha 2** {% term integration %} allows you to control a [Möhlenhoff Alpha 2](https://dev.moehlenhoff.de/en/products/room-by-room-control/oem-alpha-2-system)
 
 temperature control system.
 
diff --git a/source/_integrations/mold_indicator.markdown b/source/_integrations/mold_indicator.markdown
index 093f224d2008..47d4fb4396c5 100644
--- a/source/_integrations/mold_indicator.markdown
+++ b/source/_integrations/mold_indicator.markdown
@@ -17,7 +17,7 @@ related:
     title: Configuration file
 ---
 
-The Mold Indicator sensor {% term integration %} uses data from two temperature sensors and a humidity sensor to predict the humidity near a cold surface. High humidity may lead to mold growth at more than ~70% and causes condensation at 100%.
+The **Mold Indicator** {% term integration %} uses data from two temperature sensors and a humidity sensor to predict the humidity near a cold surface. High humidity may lead to mold growth at more than ~70% and causes condensation at 100%.
 
 The sensor data may be used, for example, to detect bad air quality (high humidity) or automate the operation of indoor air humidifiers to keep the indoor humidity at an optimum.
 
diff --git a/source/_integrations/monoprice.markdown b/source/_integrations/monoprice.markdown
index f9ca7ccade19..61ed7b013690 100644
--- a/source/_integrations/monoprice.markdown
+++ b/source/_integrations/monoprice.markdown
@@ -15,7 +15,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The `monoprice` platform allows you to control [Monoprice 6-Zone Amplifier](https://www.monoprice.com/product?p_id=10761) using a serial connection.
+The **Monoprice 6-Zone Amplifier** {% term integration %} allows you to control [Monoprice 6-Zone Amplifier](https://www.monoprice.com/product?p_id=10761) using a serial connection.
 
 {% include integrations/config_flow.md %}
 
diff --git a/source/_integrations/moon.markdown b/source/_integrations/moon.markdown
index 1fb2fd86d0ac..da3c5843569e 100644
--- a/source/_integrations/moon.markdown
+++ b/source/_integrations/moon.markdown
@@ -16,7 +16,7 @@ ha_config_flow: true
 ha_integration_type: service
 ---
 
-The Moon integration tracks the phases of the moon.
+The **Moon** {% term integration %} tracks the phases of the moon.
 
 {% include integrations/config_flow.md %}
 
diff --git a/source/_integrations/motion_blinds.markdown b/source/_integrations/motion_blinds.markdown
index 6e5ca8394850..2eaf1acd505f 100644
--- a/source/_integrations/motion_blinds.markdown
+++ b/source/_integrations/motion_blinds.markdown
@@ -17,7 +17,7 @@ ha_dhcp: true
 ha_integration_type: integration
 ---
 
-The integration allows you to control [Motionblinds](https://motionblinds.com/) from [Coulisse B.V.](https://coulisse.com/).
+The **Motionblinds** {% term integration %} allows you to control [Motionblinds](https://motionblinds.com/) from [Coulisse B.V.](https://coulisse.com/).
 
 Additionally the following brands have been reported to also work with this integration:
 
diff --git a/source/_integrations/motioneye.markdown b/source/_integrations/motioneye.markdown
index f686d0063776..3547fe80a05c 100644
--- a/source/_integrations/motioneye.markdown
+++ b/source/_integrations/motioneye.markdown
@@ -17,7 +17,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The motionEye integration allows you to integrate your
+The **motionEye** {% term integration %} allows you to integrate your
 [motionEye](https://github.com/motioneye-project/motioneye) server into Home Assistant. motionEye
 is an open source web-frontend for the motion daemon, used to centralize the management
 and visualization of multiple types of cameras.
diff --git a/source/_integrations/mpd.markdown b/source/_integrations/mpd.markdown
index fa5563974948..85a1475c0919 100644
--- a/source/_integrations/mpd.markdown
+++ b/source/_integrations/mpd.markdown
@@ -15,7 +15,7 @@ related:
 ha_config_flow: true
 ---
 
-The Music Player Daemon {% term integration %} allows you to control a [Music Player Daemon](https://www.musicpd.org/) from Home Assistant. Unfortunately, it does not allow you to manipulate the playlist (add or delete songs) or add transitions between the songs.
+The **Music Player Daemon** {% term integration %} allows you to control a [Music Player Daemon](https://www.musicpd.org/) from Home Assistant. Unfortunately, it does not allow you to manipulate the playlist (add or delete songs) or add transitions between the songs.
 
 Even though no playlist manipulation is possible, it is possible to use the `play_media` action to load an existing saved playlist as part of an automation or scene.
 
diff --git a/source/_integrations/mqtt_eventstream.markdown b/source/_integrations/mqtt_eventstream.markdown
index 18bab0e7c135..4aade121be2d 100644
--- a/source/_integrations/mqtt_eventstream.markdown
+++ b/source/_integrations/mqtt_eventstream.markdown
@@ -13,7 +13,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mqtt_eventstream` {% term integration %} connects two Home Assistant instances via MQTT.
+The **MQTT Eventstream** {% term integration %} connects two Home Assistant instances via MQTT.
 
 ## Configuration
 
diff --git a/source/_integrations/mqtt_json.markdown b/source/_integrations/mqtt_json.markdown
index 8e211bae914b..49154f53eb86 100644
--- a/source/_integrations/mqtt_json.markdown
+++ b/source/_integrations/mqtt_json.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mqtt_json` device tracker {% term integration %} allows you to detect presence by monitoring an MQTT topic for new locations. To use this platform, you specify a unique topic for each device.
+The **MQTT JSON** {% term integration %} allows you to detect presence by monitoring an MQTT topic for new locations. To use this platform, you specify a unique topic for each device.
 
 ## Configuration
 
diff --git a/source/_integrations/mqtt_room.markdown b/source/_integrations/mqtt_room.markdown
index d5353c3d2120..4f96e4ea5af5 100644
--- a/source/_integrations/mqtt_room.markdown
+++ b/source/_integrations/mqtt_room.markdown
@@ -15,7 +15,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mqtt_room` sensor {% term integration %} allows you to detect the indoor location of devices using MQTT clients.
+The **MQTT room presence** {% term integration %} allows you to detect the indoor location of devices using MQTT clients.
 
 ## Configuration
 
diff --git a/source/_integrations/mqtt_statestream.markdown b/source/_integrations/mqtt_statestream.markdown
index cf4a6fb5d5f1..a9d2cc5746d1 100644
--- a/source/_integrations/mqtt_statestream.markdown
+++ b/source/_integrations/mqtt_statestream.markdown
@@ -13,7 +13,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `mqtt_statestream` {% term integration %} publishes state changes in Home Assistant to individual MQTT topics. [The MQTT integration](/integrations/mqtt/) is a prerequisite for MQTT Statestream to work.
+The **MQTT Statestream** {% term integration %} publishes state changes in Home Assistant to individual MQTT topics. [The MQTT integration](/integrations/mqtt/) is a prerequisite for MQTT Statestream to work.
 
 ## Configuration
 
diff --git a/source/_integrations/msteams.markdown b/source/_integrations/msteams.markdown
index 32d788370996..42aa9b1dd1e4 100644
--- a/source/_integrations/msteams.markdown
+++ b/source/_integrations/msteams.markdown
@@ -14,7 +14,7 @@ ha_integration_type: integration
 ha_quality_scale: legacy
 ---
 
-The `Microsoft Teams` platform allows you to send notifications from Home Assistant to a team channel in [Microsoft Teams](https://www.microsoft.com/microsoft-teams/group-chat-software).
+The **Microsoft Teams** {% term integration %} allows you to send notifications from Home Assistant to a team channel in [Microsoft Teams](https://www.microsoft.com/microsoft-teams/group-chat-software).
 
 {% note %}
 
diff --git a/source/_integrations/mullvad.markdown b/source/_integrations/mullvad.markdown
index f7a5ee04650f..520bf23adf65 100644
--- a/source/_integrations/mullvad.markdown
+++ b/source/_integrations/mullvad.markdown
@@ -15,7 +15,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Mullvad VPN {% term integration %} uses the [Mullvad](https://mullvad.net/) VPN API to detect if your Home Assistant instance is connected to the Mullvad VPN service.
+The **Mullvad VPN** {% term integration %} uses the [Mullvad](https://mullvad.net/) VPN API to detect if your Home Assistant instance is connected to the Mullvad VPN service.
 
 ![](/images/screenshots/mullvad_vpn_sample_sensor_connected.png)
 
diff --git a/source/_integrations/mutesync.markdown b/source/_integrations/mutesync.markdown
index 9421b558bd12..f9918ee4696e 100644
--- a/source/_integrations/mutesync.markdown
+++ b/source/_integrations/mutesync.markdown
@@ -14,7 +14,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The mutesync integration for Home Assistant connects to the [mütesync virtual button](https://mutesync.com/). This tray app pairs with popular video conferencing tools such as Zoom, Google Meet, Discord, and Teams.
+The **mutesync** {% term integration %} for Home Assistant connects to the [mütesync virtual button](https://mutesync.com/). This tray app pairs with popular video conferencing tools such as Zoom, Google Meet, Discord, and Teams.
 
 With this integration, Home Assistant can track when you're in a meeting and whether your mic is muted/unmuted.
 
diff --git a/source/_integrations/notify.mqtt.markdown b/source/_integrations/notify.mqtt.markdown
index ca35109b95e7..aea6c966007e 100644
--- a/source/_integrations/notify.mqtt.markdown
+++ b/source/_integrations/notify.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The **MQTT notify** platform lets you send an MQTT message when the `send_message` action is called. This can be used to expose a action of a remote device that allows processing a message, such as showing it on a screen.
+The **MQTT notify** {% term integration %} lets you send an MQTT message when the `send_message` action is called. This can be used to expose a action of a remote device that allows processing a message, such as showing it on a screen.
 
 ## Configuration
 
diff --git a/source/_integrations/number.mqtt.markdown b/source/_integrations/number.mqtt.markdown
index 515ece525477..4008a3db5697 100644
--- a/source/_integrations/number.mqtt.markdown
+++ b/source/_integrations/number.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` Number platform allows you to integrate devices that might expose configuration options through MQTT into Home Assistant as a Number. Every time a message under the `topic` in the configuration is received, the number entity will be updated in Home Assistant and vice-versa, keeping the device and Home Assistant in-sync.
+The **MQTT Number** {% term integration %} allows you to integrate devices that might expose configuration options through MQTT into Home Assistant as a Number. Every time a message under the `topic` in the configuration is received, the number entity will be updated in Home Assistant and vice-versa, keeping the device and Home Assistant in-sync.
 
 ## Configuration
 
diff --git a/source/_integrations/raincloud.markdown b/source/_integrations/raincloud.markdown
index 792afecba5e3..f6ba12e732e5 100644
--- a/source/_integrations/raincloud.markdown
+++ b/source/_integrations/raincloud.markdown
@@ -22,7 +22,7 @@ related:
 ha_quality_scale: legacy
 ---
 
-The `raincloud` {% term integration %} allows you to integrate your [Melnor RainCloud](https://wifiaquatimer.com) sprinkler system in Home Assistant.
+The **Melnor RainCloud** {% term integration %} allows you to integrate your [Melnor RainCloud](https://wifiaquatimer.com) sprinkler system in Home Assistant.
 
 There is currently support for the following device types within Home Assistant:
 
diff --git a/source/_integrations/scene.mqtt.markdown b/source/_integrations/scene.mqtt.markdown
index e61adb97387d..7f0060faf093 100644
--- a/source/_integrations/scene.mqtt.markdown
+++ b/source/_integrations/scene.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` scene platform lets you control your MQTT enabled scenes.
+The **MQTT Scene** {% term integration %} lets you control your MQTT enabled scenes.
 
 ## Configuration
 
diff --git a/source/_integrations/select.mqtt.markdown b/source/_integrations/select.mqtt.markdown
index 8223744e27d1..f7458eb0c166 100644
--- a/source/_integrations/select.mqtt.markdown
+++ b/source/_integrations/select.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` Select platform allows you to integrate devices that might expose configuration options through MQTT into Home Assistant as a Select. Every time a message under the `topic` in the configuration is received, the select entity will be updated in Home Assistant and vice-versa, keeping the device and Home Assistant in sync.
+The **MQTT Select** {% term integration %} allows you to integrate devices that might expose configuration options through MQTT into Home Assistant as a Select. Every time a message under the `topic` in the configuration is received, the select entity will be updated in Home Assistant and vice-versa, keeping the device and Home Assistant in sync.
 
 ## Configuration
 
diff --git a/source/_integrations/sensor.mqtt.markdown b/source/_integrations/sensor.mqtt.markdown
index 5ee1d6c86bb4..2cdd6a9a1da9 100644
--- a/source/_integrations/sensor.mqtt.markdown
+++ b/source/_integrations/sensor.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-This `mqtt` sensor platform uses the MQTT message payload as the sensor value. If messages in this `state_topic` are published with *RETAIN* flag, the sensor will receive an instant update with last known value. Otherwise, the initial state will be undefined.
+The **MQTT Sensor** {% term integration %} uses the MQTT message payload as the sensor value. If messages in this `state_topic` are published with *RETAIN* flag, the sensor will receive an instant update with last known value. Otherwise, the initial state will be undefined.
 
 ## Configuration
 
diff --git a/source/_integrations/siren.mqtt.markdown b/source/_integrations/siren.mqtt.markdown
index e965a16dd40b..cdad06b527c9 100644
--- a/source/_integrations/siren.mqtt.markdown
+++ b/source/_integrations/siren.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` siren platform lets you control your MQTT enabled sirens and text based notification devices.
+The **MQTT Siren** {% term integration %} lets you control your MQTT enabled sirens and text based notification devices.
 
 ## Configuration
 
diff --git a/source/_integrations/switch.mqtt.markdown b/source/_integrations/switch.mqtt.markdown
index b6e7f348d677..c26d09a11af2 100644
--- a/source/_integrations/switch.mqtt.markdown
+++ b/source/_integrations/switch.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` switch platform lets you control your MQTT enabled switches.
+The **MQTT Switch** {% term integration %} lets you control your MQTT enabled switches.
 
 ## Configuration
 
diff --git a/source/_integrations/tag.mqtt.markdown b/source/_integrations/tag.mqtt.markdown
index 5d736f26e673..6a100b5981d3 100644
--- a/source/_integrations/tag.mqtt.markdown
+++ b/source/_integrations/tag.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` tag scanner platform uses an MQTT message payload to generate tag scanned events.
+The **MQTT tag scanner** {% term integration %} uses an MQTT message payload to generate tag scanned events.
 
 ## Configuration
 
diff --git a/source/_integrations/text.mqtt.markdown b/source/_integrations/text.mqtt.markdown
index c5ef2f956352..8db5d07d09f6 100644
--- a/source/_integrations/text.mqtt.markdown
+++ b/source/_integrations/text.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` Text platform allows you to integrate devices that show text that can be set remotely. Optionally the text state can be monitored too using MQTT.
+The **MQTT Text** {% term integration %} allows you to integrate devices that show text that can be set remotely. Optionally the text state can be monitored too using MQTT.
 
 ## Configuration
 
diff --git a/source/_integrations/update.mqtt.markdown b/source/_integrations/update.mqtt.markdown
index 6ef0c0bdec0a..0f1f4cd57a3b 100644
--- a/source/_integrations/update.mqtt.markdown
+++ b/source/_integrations/update.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_domain: mqtt
 ---
 
-The `mqtt` Update platform allows you to integrate devices that might expose firmware/software installed and the latest versions through MQTT into Home Assistant as an Update entity. Every time a message under the `topic` in the configuration is received, the entity will be updated in Home Assistant.
+The **MQTT Update** {% term integration %} allows you to integrate devices that might expose firmware/software installed and the latest versions through MQTT into Home Assistant as an Update entity. Every time a message under the `topic` in the configuration is received, the entity will be updated in Home Assistant.
 
 ## Configuration
 
diff --git a/source/_integrations/vacuum.mqtt.markdown b/source/_integrations/vacuum.mqtt.markdown
index 3a3bf2e18f70..6f17d033f8ad 100644
--- a/source/_integrations/vacuum.mqtt.markdown
+++ b/source/_integrations/vacuum.mqtt.markdown
@@ -7,7 +7,7 @@ ha_release: 0.54
 ha_domain: mqtt
 ---
 
-The `mqtt` vacuum {% term integration %} allows you to control your MQTT-enabled vacuum.
+The **MQTT Vacuum** {% term integration %} allows you to control your MQTT-enabled vacuum.
 The initial state of the MQTT vacuum {% term entity %} will set to `unknown` and can be reset by a device by sending a `null` payload as state.
 
 ## Configuration
diff --git a/source/_integrations/valve.mqtt.markdown b/source/_integrations/valve.mqtt.markdown
index 03a7a8017365..314c9f6a22c1 100644
--- a/source/_integrations/valve.mqtt.markdown
+++ b/source/_integrations/valve.mqtt.markdown
@@ -8,7 +8,7 @@ ha_release: 2024.1
 ha_domain: mqtt
 ---
 
-The `mqtt` valve platform allows you to control an MQTT valve (such a gas or water valve).
+The **MQTT Valve** {% term integration %} allows you to control an MQTT valve (such a gas or water valve).
 
 ## Configuration
 
diff --git a/source/_integrations/water_heater.mqtt.markdown b/source/_integrations/water_heater.mqtt.markdown
index 4a64a489680d..ecf0a4d0b3aa 100644
--- a/source/_integrations/water_heater.mqtt.markdown
+++ b/source/_integrations/water_heater.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Local Polling
 ha_domain: mqtt
 ---
 
-The `mqtt` water heater platform lets you control your MQTT enabled water heater devices.
+The **MQTT water heater** {% term integration %} lets you control your MQTT enabled water heater devices.
 
 ## Configuration
 
diff --git a/source/_integrations/yamaha_musiccast.markdown b/source/_integrations/yamaha_musiccast.markdown
index 3693924fe245..f518e60b7dee 100644
--- a/source/_integrations/yamaha_musiccast.markdown
+++ b/source/_integrations/yamaha_musiccast.markdown
@@ -19,7 +19,7 @@ ha_platforms:
 ha_integration_type: integration
 ---
 
-The Yamaha **MusicCast** {% term integration %} allows you to control [Yamaha MusicCast Receivers](https://usa.yamaha.com/products/audio_visual/musiccast/index.html) from Home Assistant.
+The **Yamaha MusicCast** {% term integration %} allows you to control [Yamaha MusicCast Receivers](https://usa.yamaha.com/products/audio_visual/musiccast/index.html) from Home Assistant.
 
 Supported devices are listed on their [site](https://usa.yamaha.com/products/contents/audio_visual/musiccast/musiccast-compatiblity.html).