replace instances of 'indices' with 'indexes'

Signed-off-by: alicejw <alicejw@amazon.com>

Gemfile

@@ -30,3 +30,5 @@ gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby]
 
 # Performance-booster for watching directories on Windows
 gem "wdm", "~> 0.1.0" if Gem.win_platform?
+
+gem "webrick"

_opensearch/index-alias.md

@@ -6,13 +6,13 @@ nav_order: 12
 
 # Index aliases
 
-An alias is a virtual index name that can point to one or more indices.
+An alias is a virtual index name that can point to one or more indexes.
 
-If your data is spread across multiple indices, rather than keeping track of which indices to query, you can create an alias and query it instead.
+If your data is spread across multiple indexes, rather than keeping track of which indexes to query, you can create an alias and query it instead.
 
-For example, if you’re storing logs into indices based on the month and you frequently query the logs for the previous two months, you can create a `last_2_months` alias and update the indices it points to each month.
+For example, if you’re storing logs into indexes based on the month and you frequently query the logs for the previous two months, you can create a `last_2_months` alias and update the indexes it points to each month.
 
-Because you can change the indices an alias points to at any time, referring to indices using aliases in your applications allows you to reindex your data without any downtime.
+Because you can change the indexes an alias points to at any time, referring to indexes using aliases in your applications allows you to reindex your data without any downtime.
 
 ---
 
@@ -63,7 +63,7 @@ To check if `alias1` refers to `index-1`, run the following command:
 GET alias1
 ```
 
-## Add or remove indices
+## Add or remove indexes
 
 You can perform multiple actions in the same `_aliases` operation.
 For example, the following command removes `index-1` and adds `index-2` to `alias1`:
@@ -90,7 +90,7 @@ POST _aliases
 
 The `add` and `remove` actions occur atomically, which means that at no point will `alias1` point to both `index-1` and `index-2`.
 
-You can also add indices based on an index pattern:
+You can also add indexes based on an index pattern:
 
 ```json
 POST _aliases
@@ -108,7 +108,7 @@ POST _aliases
 
 ## Manage aliases
 
-To list the mapping of aliases to indices, run the following command:
+To list the mapping of aliases to indexes, run the following command:
 
 ```json
 GET _cat/aliases?v
@@ -121,7 +121,7 @@ alias     index   filter    routing.index   routing.search
 alias1    index-1   *             -                 -
 ```
 
-To check which indices an alias points to, run the following command:
+To check which indexes an alias points to, run the following command:
 
 ```json
 GET _alias/alias1
@@ -166,7 +166,7 @@ PUT index-1
 
 ## Create filtered aliases
 
-You can create a filtered alias to access a subset of documents or fields from the underlying indices.
+You can create a filtered alias to access a subset of documents or fields from the underlying indexes.
 
 This command adds only a specific timestamp field to `alias1`:
 

_opensearch/index-data.md

@@ -68,16 +68,16 @@ PUT movies/_doc/1
 
 Because you must specify an ID, if you run this command 10 times, you still have just one document indexed with the `_version` field incremented to 10.
 
-Indices default to one primary shard and one replica. If you want to specify non-default settings, create the index before adding documents:
+Indexes default to one primary shard and one replica. If you want to specify non-default settings, create the index before adding documents:
 
 ```json
 PUT more-movies
 { "settings": { "number_of_shards": 6, "number_of_replicas": 2 } }
 ```
 
-## Naming restrictions for indices
+## Naming restrictions for indexes
 
-OpenSearch indices have the following naming restrictions:
+OpenSearch indexes have the following naming restrictions:
 
 - All letters must be lowercase.
 - Index names can't begin with underscores (`_`) or hyphens (`-`).

_opensearch/index-templates.md

@@ -6,7 +6,7 @@ nav_order: 15
 
 # Index templates
 
-Index templates let you initialize new indices with predefined mappings and settings. For example, if you continuously index log data, you can define an index template so that all of these indices have the same number of shards and replicas.
+Index templates let you initialize new indexes with predefined mappings and settings. For example, if you continuously index log data, you can define an index template so that all of these indexes have the same number of shards and replicas.
 
 ### Create a template
 
@@ -95,7 +95,7 @@ GET logs-2020-01-01
 }
 ```
 
-Any additional indices that match this pattern---`logs-2020-01-02`, `logs-2020-01-03`, and so on---will inherit the same mappings and settings.
+Any additional indexes that match this pattern---`logs-2020-01-02`, `logs-2020-01-03`, and so on---will inherit the same mappings and settings.
 
 Index patterns cannot contain any of the following characters: `:`, `"`, `+`, `/`, `\`, `|`, `?`, `#`, `>`, and `<`.
 
@@ -127,7 +127,7 @@ HEAD _index_template/<name>
 
 ### Configure multiple templates
 
-You can create multiple index templates for your indices. If the index name matches more than one template, OpenSearch merges all mappings and settings from all matching templates and applies them to the index.
+You can create multiple index templates for your indexes. If the index name matches more than one template, OpenSearch merges all mappings and settings from all matching templates and applies them to the index.
 
 The settings from the more recently created index templates override the settings of older index templates. So, you can first define a few common settings in a generic template that can act as a catch-all and then add more specialized settings as required.