diff --git a/FORMATTING_GUIDE.md b/FORMATTING_GUIDE.md index ac15540f..9c6a6b7c 100644 --- a/FORMATTING_GUIDE.md +++ b/FORMATTING_GUIDE.md @@ -156,7 +156,7 @@ If the image is under a list item, place it on a new line with a tab. For more e When describing an icon, use the icon's name followed by an inline image in parentheses. Insert the image in line with text using the `nomarkdown` extension and an HTML image: ``` -Choose the play icon ({::nomarkdown}play icon{:/}) on the top right of the request. +Choose the play icon ({::nomarkdown}play icon{:/}) on the upper right of the request. ``` ## Labels diff --git a/_clients/javascript/index.md b/_clients/javascript/index.md index 6f4d693e..ba58ad04 100644 --- a/_clients/javascript/index.md +++ b/_clients/javascript/index.md @@ -3,6 +3,8 @@ layout: default title: JavaScript client has_children: true nav_order: 40 +redirect_from: + - /clients/javascript/ --- # JavaScript client diff --git a/_clients/python-low-level.md b/_clients/python-low-level.md index 14919a8e..74920f0b 100644 --- a/_clients/python-low-level.md +++ b/_clients/python-low-level.md @@ -2,6 +2,8 @@ layout: default title: Low-level Python client nav_order: 10 +redirect_from: + - /clients/python/ --- # Low-level Python client diff --git a/_install-and-configure/install-opensearch/docker.md b/_install-and-configure/install-opensearch/docker.md index fd651a9d..67058a05 100644 --- a/_install-and-configure/install-opensearch/docker.md +++ b/_install-and-configure/install-opensearch/docker.md @@ -209,6 +209,7 @@ volumes: networks: opensearch-net: ``` +{% include copy.html %} If you override `opensearch_dashboards.yml` settings using environment variables in your compose file, use all uppercase letters and replace periods with underscores (for example, for `opensearch.hosts`, use `OPENSEARCH_HOSTS`). This behavior is inconsistent with overriding `opensearch.yml` settings, where the conversion is just a change to the assignment operator (for example, `discovery.type: single-node` in `opensearch.yml` is defined as `discovery.type=single-node` in `docker-compose.yml`). {: .note} diff --git a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md index 8d83a046..2f25bd55 100644 --- a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md +++ b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md @@ -168,7 +168,7 @@ The following table lists benchmarking results for the `nyc_taxi` dataset with t -As the size of the workload increases, the benefits of segment replication are amplified because the replicas are not required to index the larger dataset. In general, segment replication leads to higher throughput at lower resource cost than document replication in all cluster configurations, not accounting for replication lag. +As the size of the workload increases, the benefits of segment replication are amplified because the replicas are not required to index the larger dataset. In general, segment replication leads to higher throughput at lower resource costs than document replication in all cluster configurations, not accounting for replication lag. ### Increasing the number of primary shards