Rename installation method to installation type (#40789)

c0ffeeca7 · Copilot · web-flow · commit ce4102a53918 · 2025-09-09T11:54:42.000-04:00
Co-authored-by: Copilot &lt;175728472+Copilot@users.noreply.github.com&gt;
diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml
@@ -79,7 +79,7 @@
     Home Assistant has built-in functionality to create files containing a copy
     of your configuration. This can be used to restore your Home Assistant as
     well as migrate to a new system. The backup feature is available for all
-    [installation types](/installation/#about-installation-methods).
+    [installation types](/installation/#about-installation-types).
   link: /common-tasks/general/#backups
   aliases:
     - backups
@@ -307,23 +307,23 @@
     Home Assistant Container is a standalone container-based installation of
     Home Assistant Core. Any [OCI](https://opencontainers.org/) compatible
     runtime can be used, but the documentation focus is on Docker.
-  link: /installation/#about-installation-methods
+  link: /installation/#about-installation-types
 - term: Home Assistant Core
   definition: >-
     Home Assistant Core is the Python program at the heart of Home Assistant. It
     is part of all installation types. It can be installed standalone (without Home Assistant
     Supervisor) as a container using Docker (this is typically referred to as the Home Assistant
-    Container installation method). For development, Core can also be run using a Virtual
-    Environment (previously referred as the Home Assistant Core installation method.
-    For production setup, the [Home Assistant Core installation method is deprecated](https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/).
+    Container installation type). For development, Core can also be run using a Virtual
+    Environment (previously referred as the Home Assistant Core installation type.
+    For production setup, the [Home Assistant Core installation type is deprecated](https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/).
 - term: Home Assistant Supervised
   definition: >-
-    The Home Assistant Supervised installation method is a full UI managed home automation ecosystem
+    The Home Assistant Supervised installation type is a full UI managed home automation ecosystem
     that runs the Home Assistant Core program, the Home Assistant Supervisor and
     add-ons. It comes pre-installed on Home Assistant OS, but can be installed
     standalone on Debian Linux systems. It leverages Docker, which is managed by
     the Home Assistant Supervisor. The
-    [Home Assistant Supervised installation method is deprecated](https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/).  
+    [Home Assistant Supervised installation type is deprecated](https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/).  
 - term: Home Assistant Supervisor
   definition: >-
     The Home Assistant Supervisor is a program that manages a Home Assistant
@@ -337,7 +337,7 @@
     includes Home Assistant Core, the Home Assistant Supervisor, and supports
     add-ons. Home Assistant Supervisor keeps it up to date, removing the need
     for you to manage an operating system. Home Assistant Operating System is
-    the recommended installation method for most users.
+    the recommended installation type for most users.
 - term: Host
   definition: >-
     A device that can communicate with other devices on a network. During setup
diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown
@@ -86,7 +86,7 @@ If you do not want to [re-import the blueprint](/docs/automation/using_blueprint
 its {% term YAML %} content to keep it up to date:
 
 1. Navigate to the blueprints directory (`blueprints/automation/`).
-   The location of this directory depends on the installation method. It's
+   The location of this directory depends on the installation type. It's
    similar to how you find [`configuration.yaml`](/docs/configuration/#editing-configurationyaml).
 2. Next, you must find the blueprint to update. The path name of a blueprint consists of:
    - The username of the user that created it. The name depends on the source of the blueprint:
diff --git a/source/_docs/configuration.markdown b/source/_docs/configuration.markdown
@@ -27,7 +27,7 @@ Example of a configuration.yaml file, accessed using the File editor add-on on a
 
 ## Editing `configuration.yaml`
 
-How you edit your `configuration.yaml` file depends on your editor preferences and the [installation method](/installation/#about-installation-methods) you used to set up Home Assistant. Follow these steps:
+How you edit your `configuration.yaml` file depends on your editor preferences and the [installation type](/installation/#about-installation-types) you used to set up Home Assistant. Follow these steps:
 
 1. [Set up file access](#to-set-up-access-to-the-files-and-prepare-an-editor).
 2. [Locate the config directory](#to-find-the-configuration-directory).
@@ -37,7 +37,7 @@ How you edit your `configuration.yaml` file depends on your editor preferences a
 ### To set up access to the files and prepare an editor
 
 Before you can edit a file, you need to know how to access files in Home Assistant and setup an editor.
-File access depends on your [installation method](/installation/#about-installation-methods). If you use {% term "Home Assistant Operating System" %}, you can use editor add-ons, for example. If you use {% term "Home Assistant Container" %}, add-ons are not available.
+File access depends on your [installation type](/installation/#about-installation-types). If you use {% term "Home Assistant Operating System" %}, you can use editor add-ons, for example. If you use {% term "Home Assistant Container" %}, add-ons are not available.
 
 To set up file access on the Home Assistant Operating System, follow these steps:
 
@@ -70,7 +70,7 @@ If you have watched any videos about setting up Home Assistant using `configurat
 
 After changing configuration or automation files, you can check if the configuration is valid. A configuration check is also applied automatically when you reload the configuration or when you restart Home Assistant.
 
-The method for running a configuration check depends on your [installation type](/installation/#about-installation-methods). Check the common tasks for your installation type:
+The method for running a configuration check depends on your [installation type](/installation/#about-installation-types). Check the common tasks for your installation type:
 
 - [Configuration check on Operating System](/common-tasks/os/#configuration-check)
 - [Configuration check on Container](/common-tasks/container/#configuration-check)
diff --git a/source/_docs/tools/hass.markdown b/source/_docs/tools/hass.markdown
@@ -5,7 +5,7 @@ description: "Description of hass."
 
 The command-line part of Home Assistant is `hass`.
 
-This tool is only available to users of the Home Assistant Core installation method. It is started from the command line on the computer running Home Assistant Core (accessed perhaps via SSH).
+This tool is only available to users of the Home Assistant Core installation type. It is started from the command line on the computer running Home Assistant Core (accessed perhaps via SSH).
 
 ```text
 $ hass -h
diff --git a/source/_faq/ha-vs-hassio.markdown b/source/_faq/ha-vs-hassio.markdown
@@ -5,7 +5,7 @@ ha_category: Installation
 ---
 
 Home Assistant Core is a Python program, in simple words. It can be run on various operating systems and provide the ability to track, control and automate your devices.
-When people talking about Home Assistant Core they usually refer to a standalone [installation method](/docs/installation/).
+When people talking about Home Assistant Core they usually refer to a standalone [installation type](/docs/installation/).
 
 [Home Assistant](/hassio/) is a combination of Home Assistant Core and tools which allows one to run it easily on a Raspberry Pi and other platforms without setting up an operating system first.
 Home Assistant is an all-in one-solution and has a management user interface that can be used from the Home Assistant frontend. This interface is not present in a Home Assistant Core setup.
diff --git a/source/_includes/installation/container.md b/source/_includes/installation/container.md
@@ -4,7 +4,7 @@
 These below instructions are for an installation of {% term "Home Assistant Container" %} running in your own container environment, which you manage yourself. Any [OCI](https://opencontainers.org/) compatible runtime can be used, however this guide will focus on installing it with Docker.
 
 {% note %}
-This installation method **does not have access to add-ons**. If you want to use add-ons, you need to use another installation method. The recommended method is {% term "Home Assistant Operating System" %}. Checkout the [overview table of installation types](https://www.home-assistant.io/installation/#about-installation-methods) to see the differences.
+This installation type **does not have access to add-ons**. If you want to use add-ons, you need to use another installation type. The recommended type is {% term "Home Assistant Operating System" %}. Checkout the [overview table of installation types](https://www.home-assistant.io/installation/#about-installation-types) to see the differences.
 {% endnote %}
 
 {% important %}
diff --git a/source/_integrations/go2rtc.markdown b/source/_integrations/go2rtc.markdown
@@ -17,7 +17,7 @@ ha_quality_scale: internal
 go2rtc is an open source project providing a camera streaming application that supports formats such as RTSP, WebRTC, HomeKit, FFmpeg, RTMP.  The **go2rtc** {% term integration %} connects to a go2rtc instance and provides a WebRTC proxy for all your cameras. To learn more about go2rtc, refer to the [project's GitHub page](https://github.com/AlexxIT/go2rtc/).
 
 
-If you are using the [`default_config`](/integrations/default_config/) and run Home Assistant using one of the following installation methods, the go2rtc integration will be set up automatically and you don't need to do anything:
+If you are using the [`default_config`](/integrations/default_config/) and run Home Assistant using one of the following installation types, the go2rtc integration will be set up automatically and you don't need to do anything:
 
 - {% term "Home Assistant Operating System" %}
 - {% term "Home Assistant Supervised" %}
diff --git a/source/_integrations/lacrosse.markdown b/source/_integrations/lacrosse.markdown
@@ -37,7 +37,7 @@ Or, when using Docker containers:
 docker exec -it <containername> pylacrosse -d /dev/ttyUSB0 scan
 ```
 
-If you are using the Home Assistant OS or Supervised installation method, these
+If you are using the Home Assistant OS or Supervised installation types, these
 methods are not available for you. The use of an additional computer to figure
 out the ID is advised.
 
diff --git a/source/_redirects b/source/_redirects
@@ -345,6 +345,7 @@ layout: null
 /ecosystem/notebooks/stats https://data.home-assistant.io
 /examples/notify.mqtt /integrations/mqtt/#mqtt-notifications
 /ios/whats-new https://companion.home-assistant.io/docs/getting_started/getting-started
+/installation/#about-installation-methods /installation/#about-installation-types
 /installation/nuc /installation/generic-x86-64
 /integrations/auth /docs/authentication
 /integrations/automation /docs/automation
diff --git a/source/installation/index.html b/source/installation/index.html
@@ -20,8 +20,7 @@
   <h2>Plug and play with Home Assistant Green</h2>
   <p>
     The affordable Home Assistant Green is the easiest way to start using
-    Home Assistant. It's plug-and-play and comes with Home Assistant already
-    installed.
+    Home Assistant. It's plug-and-play and comes with [Home Assistant Operating System](/installation/#about-installation-types) already installed.
   </p>
 
   <div class="installations-card">
@@ -515,9 +514,9 @@ <h3>Install Home Assistant on other systems</h3>
   </div>
 </div>
 
-  <h3>Deprecated installation methods</h3>
+  <h3>Deprecated installation types</h3>
   <p>
-    Home Assistant used to offer two additional installation methods for advanced users: <b>{% term "Home Assistant Core" %}</b> and <b>{% term "Home Assistant Supervised" %}</b>. These two methods are now <a href="https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/">deprecated and no longer recommended for new users</a>.
+    Home Assistant used to offer two additional installation types for advanced users: <b>{% term "Home Assistant Core" %}</b> and <b>{% term "Home Assistant Supervised" %}</b>. These two methods are now <a href="https://www.home-assistant.io/blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/">deprecated and no longer recommended for new users</a>.
   </p>
   <ul>
     <li>
