diff --git a/_config.yml b/_config.yml
index 408db250ad3..034eb77c927 100644
--- a/_config.yml
+++ b/_config.yml
@@ -183,7 +183,7 @@ installation:
     raspberrypi3: "ghcr.io/home-assistant/raspberrypi3-homeassistant"
     raspberrypi4: "ghcr.io/home-assistant/raspberrypi4-homeassistant"
   versions:
-    python: "3.8"
+    python: "3.9"
   types:
     odroid:
       board: ODROID
diff --git a/source/_includes/installation/core.md b/source/_includes/installation/core.md
index 6bf609b222d..decd259184a 100644
--- a/source/_includes/installation/core.md
+++ b/source/_includes/installation/core.md
@@ -8,15 +8,22 @@ To install Home Assistant Core on Windows, you will need to use the Windows Subs
 As an alternative, Home Assistant OS can be installed in a Linux guest VM. Running Home Assistant Core directly on Windows is not supported.
 {% endif %}
 
+<div class='note warning'>
+
+This is an advanced installation process, and some steps might differ on your system. Considering the nature of this installation type, we assume you can handle subtle differences between this document and the system configuration you are using. When in doubt, please consider one of the [other installation methods](/installation/), as they might be a better fit instead.
+
+</div>
+
 <div class='note'>
 <b>Prerequisites</b>
 
 This guide assumes that you already have an operating system setup and have installed Python {{site.installation.versions.python}} (including the package `python3-dev`) or newer.
+
 </div>
 
 ### Install dependencies
 
-Before you start make sure your system is fully updated, all packages in this guide are installed with `apt`, if your OS does not have that, look for alternatives.
+Before you start, make sure your system is fully updated, all packages in this guide are installed with `apt`, if your OS does not have that, look for alternatives.
 
 ```bash
 sudo apt-get update
@@ -26,9 +33,11 @@ sudo apt-get upgrade -y
 Install the dependencies:
 
 ```bash
-sudo apt-get install -y python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 libturbojpeg tzdata
+sudo apt-get install -y python3 python3-dev python3-venv python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 libturbojpeg0 tzdata
 ```
 
+The above-listed dependencies might differ or missing, depending on your system or personal use of Home Assistant.
+
 ### Create an account
 
 Add an account for Home Assistant Core called `homeassistant`.
@@ -72,7 +81,7 @@ Once you have activated the virtual environment (notice the prompt change to `(h
 python3 -m pip install wheel
 ```
 
-Once you have installed the required Python package it is now time to install Home Assistant Core!
+Once you have installed the required Python package, it is now time to install Home Assistant Core!
 
 ```bash
 pip3 install homeassistant
diff --git a/source/_integrations/ialarm.markdown b/source/_integrations/ialarm.markdown
index 54055ac32ce..07871db609a 100644
--- a/source/_integrations/ialarm.markdown
+++ b/source/_integrations/ialarm.markdown
@@ -1,7 +1,6 @@
 ---
 title: Antifurto365 iAlarm
 description: Instructions on how to integrate iAlarms alarms into Home Assistant.
-logo: antifurto365-ialarm.png
 ha_category:
   - Alarm
 ha_iot_class: Local Polling
diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown
index 8e9343bfeed..82867e5dd89 100644
--- a/source/_integrations/plex.markdown
+++ b/source/_integrations/plex.markdown
@@ -30,7 +30,7 @@ If a Plex server has been claimed by a Plex account via the [claim interface](ht
 
 {% include integrations/config_flow.md %}
 
-During setup, the integration will check all possible ways to connect to your Plex server(s) - i.e., local or public addresses, HTTP or HTTPS, by IP or using a subdomain of `plex.direct`, or by using a Plex relay if all other methods fail. The integration will prefer local over public and secure over insecure, in that order. The selected address is shown on the Plex card on the Integrations page.
+During setup, you will need to log in as a server administrator. The integration will check all possible ways to connect to your Plex server(s) - i.e., local or public addresses, HTTP or HTTPS, by IP or using a subdomain of `plex.direct`, or by using a Plex relay if all other methods fail. The integration will prefer local over public and secure over insecure, in that order. The selected address is shown on the Plex card on the Integrations page.
 
 If your router enforces DNS rebind protection, connections to the local `plex.direct` hostname may fail (see [Plex documentation](https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/#dnsrebinding)). To avoid this, configure your router to allow DNS rebinding for `plex.direct` by following the instructions in the documentation link.