Updates the Install TOC (#3031)

* updates changes to install toc

Signed-off-by: Heather Halter <hdhalter@amazon.com>

* cleanup files

Signed-off-by: Heather Halter <hdhalter@amazon.com>

* capital letter

Signed-off-by: Heather Halter <hdhalter@amazon.com>

---------

Signed-off-by: Heather Halter <hdhalter@amazon.com>

_config.yml

@@ -99,10 +99,10 @@ just_the_docs:
   # Define the collections used in the theme
   collections:
     install-and-configure:
-      name: Install and configure
+      name: Install and upgrade
       nav_fold: true
     upgrade-to:
-      name: Upgrade to OpenSearch
+      name: Migrate to OpenSearch
       # nav_exclude: true
       nav_fold: true
       # search_exclude: true

_upgrade-to/dashboards-upgrade-to.md

@@ -1,17 +1,17 @@
 ---
 layout: default
-title: Upgrade from Kibana OSS to OpenSearch Dashboards
+title: Migrating from Kibana OSS to OpenSearch Dashboards
 nav_order: 50
 ---
 
-# Upgrade from Kibana OSS to OpenSearch Dashboards
+# Migrating from Kibana OSS to OpenSearch Dashboards
 
-Kibana OSS stores its visualizations and dashboards in one or more indices (`.kibana*`) on the Elasticsearch OSS cluster. As such, the most important step is to leave those indices intact as you upgrade from Elasticsearch OSS to OpenSearch.
+Kibana OSS stores its visualizations and dashboards in one or more indexes (`.kibana*`) on the Elasticsearch OSS cluster. As such, the most important step is to leave those indexes intact as you migrate from Elasticsearch OSS to OpenSearch.
 
-Consider exporting all Kibana objects prior to starting the upgrade. In Kibana, choose **Stack Management**, **Saved Objects**, **Export objects**.
+Consider exporting all Kibana objects prior to starting the migration. In Kibana, choose **Stack Management**, **Saved Objects**, **Export objects**.
 {: .tip }
 
-1. After you upgrade your Elasticsearch OSS cluster to OpenSearch, stop Kibana.
+1. After you migrate your Elasticsearch OSS cluster to OpenSearch, stop Kibana.
 
 1. For safety, make a backup copy of `<kibana-dir>/config/kibana.yml`.
 
@@ -19,9 +19,9 @@ Consider exporting all Kibana objects prior to starting the upgrade. In Kibana,
 
 1. Port your settings from `<kibana-dir>/config/kibana.yml` to `<dashboards-dir>/config/opensearch_dashboards.yml`.
 
-   In general, settings with `elasticsearch` in their names map to `opensearch` (e.g. `elasticsearch.shardTimeout` and `opensearch.shardTimeout`) and settings with `kibana` in their names map to `opensearchDashboards` (e.g. `kibana.defaultAppId` and `opensearchDashboards.defaultAppId`). Most other settings use the same names.
+   In general, settings with `elasticsearch` in their names map to `opensearch` (for example, `elasticsearch.shardTimeout` and `opensearch.shardTimeout`) and settings with `kibana` in their names map to `opensearchDashboards` (for example, `kibana.defaultAppId` and `opensearchDashboards.defaultAppId`). Most other settings use the same names.
 
-   For a full list of OpenSearch Dashboards settings, see [here](https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/config/opensearch_dashboards.yml){:target='\_blank'}.
+   For a full list of OpenSearch Dashboards settings, see [opensearch_dashboards.yml](https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/config/opensearch_dashboards.yml){:target='\_blank'}.
 
 1. If your OpenSearch cluster uses the security plugin, preserve and modify the default settings in `opensearch_dashboards.yml`, particularly `opensearch.username` and `opensearch.password`.
 

_upgrade-to/docker-upgrade-to.md

@@ -1,12 +1,12 @@
 ---
 layout: default
-title: Upgrade Docker clusters to OpenSearch
+title: Migrating Docker clusters to OpenSearch
 nav_order: 25
 ---
 
-# Upgrade Docker clusters to OpenSearch
+# Migrating Docker clusters to OpenSearch
 
-If you use a container orchestration system like Kubernetes (or manage your containers manually) and want to avoid downtime, think of the process not as an upgrade of each node, but as a decommissioning and replacement of each node. One by one, add OpenSearch nodes to the cluster and remove Elasticsearch OSS nodes, pointing to existing data volumes as necessary and allowing time for all indices to return to a green status prior to proceeding.
+If you use a container orchestration system like Kubernetes (or manage your containers manually) and want to avoid downtime, think of the process not as an upgrade of each node, but as a decommissioning and replacement of each node. One by one, add OpenSearch nodes to the cluster and remove Elasticsearch OSS nodes, pointing to existing data volumes as necessary and allowing time for all indexes to return to a green status prior to proceeding.
 
 If you use Docker Compose, we highly recommend that you perform what amounts to a [cluster restart upgrade]({{site.url}}{{site.baseurl}}/upgrade-to/upgrade-to/). Update your cluster configuration with new images, new settings, and new environment variables, and test it. Then stop and start the cluster. This process requires downtime, but takes very few steps and lets you continue to treat the cluster as a single entity that you can reliably deploy and redeploy.
 

_upgrade-to/index.md

@@ -1,14 +1,14 @@
 ---
 layout: default
-title: About the process
+title: About the migration process
 nav_order: 1
 redirect_from:
   - /upgrade-to/
 ---
 
-# About the process
+# About the migration process
 
-The process of upgrading from Elasticsearch OSS to OpenSearch varies depending on your current version of Elasticsearch OSS, installation type, tolerance for downtime, and cost-sensitivity. Rather than concrete steps to cover every situation, we have general guidance for the process.
+The process of migrating from Elasticsearch OSS to OpenSearch varies depending on your current version of Elasticsearch OSS, installation type, tolerance for downtime, and cost-sensitivity. Rather than concrete steps to cover every situation, we have general guidance for the process.
 
 Three approaches exist:
 

_upgrade-to/snapshot-migrate.md

@@ -1,10 +1,10 @@
 ---
 layout: default
-title: Use snapshots to migrate data
+title: Using snapshots to migrate data
 nav_order: 5
 ---
 
-# Use snapshots to migrate data
+# Using snapshots to migrate data
 
 One popular approach is to take a [snapshot]({{site.url}}{{site.baseurl}}/opensearch/snapshots/snapshot-restore) of your Elasticsearch OSS 6.x or 7.x indexes, [create an OpenSearch cluster]({{site.url}}{{site.baseurl}}/opensearch/install/), restore the snapshot on the new cluster, and point your clients to the new host.
 

_upgrade-to/upgrade-to.md

@@ -1,33 +1,33 @@
 ---
 layout: default
-title: Upgrade from Elasticsearch OSS to OpenSearch
+title: Migrating from Elasticsearch OSS to OpenSearch
 nav_order: 15
 ---
 
-# Upgrade from Elasticsearch OSS to OpenSearch
+# Migrating from Elasticsearch OSS to OpenSearch
 
-If you want to upgrade from an existing Elasticsearch OSS cluster to OpenSearch and find the [snapshot approach]({{site.url}}{{site.baseurl}}/upgrade-to/snapshot-migrate/) unappealing, you can upgrade your existing nodes from Elasticsearch OSS to OpenSearch.
+If you want to migrate from an existing Elasticsearch OSS cluster to OpenSearch and find the [snapshot approach]({{site.url}}{{site.baseurl}}/upgrade-to/snapshot-migrate/) unappealing, you can migrate your existing nodes from Elasticsearch OSS to OpenSearch.
 
 If your existing cluster runs an older version of Elasticsearch OSS, the first step is to upgrade to version 6.x or 7.x. Elasticsearch OSS supports two types of upgrades: rolling and cluster restart.
 
 - Rolling upgrades let you shut down one node at a time for minimal disruption of service.
 
-  Rolling upgrades work between minor versions (e.g. 6.5 to 6.8) and also support a single path to the next major version (e.g. 6.8 to 7.10.2). Performing these upgrades might require intermediate upgrades to arrive at your desired version and can affect cluster performance as nodes leave and rejoin, but the cluster remains available throughout the process.
+  Rolling upgrades work between minor versions (for example, 6.5 to 6.8) and also support a single path to the next major version (for example, 6.8 to 7.10.2). Performing these upgrades might require intermediate upgrades to arrive at your desired version and can affect cluster performance as nodes leave and rejoin, but the cluster remains available throughout the process.
 
 - Cluster restart upgrades require you to shut down all nodes, perform the upgrade, and restart the cluster.
 
-  Cluster restart upgrades work between minor versions (e.g. 6.5 to 6.8) and the next major version (for example, 6.x to 7.10.2). Cluster restart upgrades are faster to perform and require fewer intermediate upgrades, but require downtime.
+  Cluster restart upgrades work between minor versions (for example, 6.5 to 6.8) and the next major version (for example, 6.x to 7.10.2). Cluster restart upgrades are faster to perform and require fewer intermediate upgrades, but require downtime.
 
 
-## Upgrade paths
+## Migration paths
 
 Elasticsearch OSS version | Rolling upgrade path | Cluster restart upgrade path
 :--- | :--- | :---
-5.x | Upgrade to 5.6, upgrade to 6.8, reindex all 5.x indices, upgrade to 7.10.2, and upgrade to OpenSearch. | Upgrade to 6.8, reindex all 5.x indices, and upgrade to OpenSearch.
+5.x | Upgrade to 5.6, upgrade to 6.8, reindex all 5.x indexes, upgrade to 7.10.2, and migrate to OpenSearch. | Upgrade to 6.8, reindex all 5.x indexes, and migrate to OpenSearch.
-6.x | Upgrade to 6.8, upgrade to 7.10.2, and upgrade to OpenSearch. | Upgrade to OpenSearch.
+6.x | Upgrade to 6.8, upgrade to 7.10.2, and migrate to OpenSearch. | Migrate to OpenSearch.
-7.x | Upgrade to OpenSearch. | Upgrade to OpenSearch.
+7.x | Migrate to OpenSearch. | Migrate to OpenSearch.
 
-If you are upgrading an Open Distro for Elasticsearch cluster, we recommend first upgrading to ODFE 1.13 and then upgrading to OpenSearch.
+If you are migrating an Open Distro for Elasticsearch cluster, we recommend first upgrading to ODFE 1.13 and then migrating to OpenSearch.
 {: .note }
 
 
@@ -62,7 +62,7 @@ If you are upgrading an Open Distro for Elasticsearch cluster, we recommend firs
    sudo yum install elasticsearch-oss-7.10.2 --enablerepo=elasticsearch
    ```
 
-   For tarball installations, extract to a new directory to ensure you **do not overwrite** your `config`, `data`, and `logs` directories. Ideally, these directories should have their own, independent paths and *not* be colocated with the Elasticsearch application directory. Then set the `ES_PATH_CONF` environment variable to the directory that contains `elasticsearch.yml` (e.g. `/etc/elasticesarch/`). In `elasticsearch.yml`, set `path.data` and `path.logs` to your `data` and `logs` directories (e.g. `/var/lib/elasticsearch` and `/var/log/opensearch`).
+   For tarball installations, extract to a new directory to ensure you **do not overwrite** your `config`, `data`, and `logs` directories. Ideally, these directories should have their own, independent paths and *not* be colocated with the Elasticsearch application directory. Then set the `ES_PATH_CONF` environment variable to the directory that contains `elasticsearch.yml` (for example, `/etc/elasticesarch/`). In `elasticsearch.yml`, set `path.data` and `path.logs` to your `data` and `logs` directories (for example, `/var/lib/elasticsearch` and `/var/log/opensearch`).
 
 1. Restart Elasticsearch OSS on the node (rolling) or all nodes (cluster restart).
 
@@ -83,7 +83,7 @@ If you are upgrading an Open Distro for Elasticsearch cluster, we recommend firs
    curl -XGET 'https://localhost:9200/_nodes/_all?pretty=true' -u 'admin:admin' -k
    ```
 
-   Specifically, check the `nodes.<node-id>.version` portion of the response. Also check `_cat/indices?v` for a green status on all indices.
+   Specifically, check the `nodes.<node-id>.version` portion of the response. Also check `_cat/indices?v` for a green status on all indexes.
 
 1. (Rolling) Repeat steps 2--5 until all nodes are using the new version.
 
@@ -98,12 +98,12 @@ If you are upgrading an Open Distro for Elasticsearch cluster, we recommend firs
    }
    ```
 
-1. If you upgraded from 5.x to 6.x, [reindex]({{site.url}}{{site.baseurl}}/opensearch/reindex-data/) all indices.
+1. If you upgraded from 5.x to 6.x, [reindex]({{site.url}}{{site.baseurl}}/opensearch/reindex-data/) all indexes.
 
 1. Repeat all steps as necessary until you arrive at your desired Elasticsearch OSS version.
 
 
-## Upgrade to OpenSearch
+## Migrate to OpenSearch
 
 1. Disable shard allocation to prevent Elasticsearch OSS from replicating shards as you shut down nodes:
 
@@ -132,7 +132,7 @@ If you are upgrading an Open Distro for Elasticsearch cluster, we recommend firs
 
    1. (Optional) Copy or move your Elasticsearch OSS `data` and `logs` directories to new paths. For example, you might move `/var/lib/elasticsearch` to `/var/lib/opensearch`.
 
-   1. Set the `OPENSEARCH_PATH_CONF` environment variable to the directory that contains `opensearch.yml` (e.g. `/etc/opensearch`).
+   1. Set the `OPENSEARCH_PATH_CONF` environment variable to the directory that contains `opensearch.yml` (for example, `/etc/opensearch`).
 
    1. In `opensearch.yml`, set `path.data` and `path.logs`. You might also want to disable the security plugin for now. `opensearch.yml` might look something like this:
 
@@ -165,7 +165,7 @@ If you are upgrading an Open Distro for Elasticsearch cluster, we recommend firs
    curl -XGET -k -u 'admin:admin' 'https://localhost:9200/_nodes/_all?pretty=true'
    ```
 
-   Specifically, check the `nodes.<node-id>.version` portion of the response. Also check `_cat/indices?v` for a green status on all indices.
+   Specifically, check the `nodes.<node-id>.version` portion of the response. Also check `_cat/indices?v` for a green status on all indexes.
 
 1. (Rolling) Repeat steps 2--5 until all nodes are using OpenSearch.
 

documentation-website

@@ -0,0 +1 @@
+Subproject commit 1e274173d0bffb82ddd20549a502e4d76a3cdcc4