Fixes to redirects

_api-reference/cat/cat-cluster_manager.md

@@ -2,7 +2,8 @@
 layout: default
 title: CAT cluster manager
 parent: CAT API
-
+redirect_from:
+ - /opensearch/rest-api/cat/cat-master/
 nav_order: 30
 has_children: false
 ---

_api-reference/document-apis/index-document.md

@@ -4,7 +4,7 @@ title: Index document
 parent: Document APIs
 nav_order: 1
 redirect_from: 
- - /opensearch/rest-api/document-apis/index-document
+ - /opensearch/rest-api/document-apis/index-document/
 ---
 
 # Index document

_api-reference/document-apis/multi-get.md

@@ -4,14 +4,14 @@ title: Multi-get document
 parent: Document APIs
 nav_order: 30
 redirect_from: 
- - /opensearch/rest-api/document-apis/mulit-get/
+ - /opensearch/rest-api/document-apis/multi-get/
 ---
 
 # Multi-get documents
 Introduced 1.0 
 {: .label .label-purple }
 
-The multi-get operation allows you to execute multiple GET operations in one request, so you can get back all documents that match your criteria.
+The multi-get operation allows you to run multiple GET operations in one request, so you can get back all documents that match your criteria.
 
 ## Example without specifying index in URL
 

_api-reference/document-apis/reindex.md

@@ -4,7 +4,8 @@ title: Reindex document
 parent: Document APIs
 nav_order: 60
 redirect_from: 
- - /opensearch/reindex-data/
+  - /opensearch/reindex-data/
+  - /opensearch/rest-api/document-apis/reindex/
 ---
 
 # Reindex document

_api-reference/index-apis/put-mapping.md

@@ -5,6 +5,7 @@ parent: Index APIs
 nav_order: 27
 redirect_from:
   - /opensearch/rest-api/index-apis/update-mapping/
+  - /opensearch/rest-api/update-mapping/
 ---
 
 # Create or update mappings

_im-plugin/ism/managedindexes.md

@@ -4,6 +4,8 @@ title: Managed indexes
 nav_order: 3
 parent: Index State Management
 has_children: false
+redirect_from: 
+ - /im-plugin/ism/managedindices/
 ---
 
 # Managed indexes

_install-and-configure/configuration.md

@@ -4,6 +4,7 @@ title: Configuring OpenSearch
 nav_order: 10
 redirect_from:
  - /install-and-configure/configuration/
+  - /opensearch/configuration/
 ---
 
 # Configuring OpenSearch

_install-and-configure/install-dashboards/plugins.md

@@ -3,7 +3,7 @@ layout: default
 title: Managing OpenSearch Dashboards plugins
 nav_order: 100
 redirect_from: 
-  - /dashboards/install/plugins
+  - /dashboards/install/plugins/
   - /install-and-configure/install-dashboards/plugins/
 ---
 
@@ -149,7 +149,7 @@ sudo bin/opensearch-dashboards-plugin remove <plugin-name>
 
 Then remove all associated entries from `opensearch_dashboards.yml`.
 
-For certain plugins, you must also remove the "optimze" bundle. This is a sample command for the Anomaly Detection plugin:
+For certain plugins, you must also remove the "optimize" bundle. This is a sample command for the Anomaly Detection plugin:
 
 ```bash
 sudo rm /usr/share/opensearch-dashboards/optimize/bundles/opensearch-anomaly-detection-opensearch-dashboards.*
@@ -181,7 +181,7 @@ OpenSearch Dashboards doesn’t update plugins. Instead, you have to remove the
 
 1. Restart OpenSearch Dashboards.
 
-For example, to remove and reinstall the anomaly detection plugin:
+For example, to remove and reinstall the Anomaly Detection plugin:
 
 ```bash
 sudo bin/opensearch-plugin remove opensearch-anomaly-detection

_observing-your-data/notebooks.md

@@ -3,7 +3,7 @@ layout: default
 title: Notebooks
 nav_order: 50
 redirect_from: 
-  - /notebooks/
+  - /dashboards/notebooks/
   - /observability-plugin/notebooks/
 has_children: false
 ---

_observing-your-data/trace/getting-started.md

@@ -5,6 +5,7 @@ parent: Trace Analytics
 nav_order: 1
 redirect_from:
   - /observability-plugin/trace/get-started/
+  - /monitoring-plugins/trace/get-started/
 ---
 
 # Getting started with Trace Analytics

_observing-your-data/trace/index.md

@@ -6,6 +6,7 @@ has_children: true
 has_toc: false
 redirect_from:
   - /observability-plugin/trace/index/
+  - /monitoring-plugins/trace/index/
 ---
 
 # Trace Analytics

_observing-your-data/trace/ta-dashboards.md

@@ -5,6 +5,7 @@ parent: Trace Analytics
 nav_order: 50
 redirect_from:
   - /observability-plugin/trace/ta-dashboards/
+  - /monitoring-plugins/trace/ta-dashboards/
 ---
 
 # Trace Analytics OpenSearch Dashboards plugin
@@ -15,7 +16,7 @@ The **Dashboard** view groups traces together by HTTP method and path so that yo
 
 ![Dashboard view]({{site.url}}{{site.baseurl}}/images/ta-dashboard.png)
 
-To drill down on the traces that make up a trace group, choose the number of traces in righthand column. Then choose an individual trace for a detailed summary.
+To drill down on the traces that make up a trace group, choose the number of traces in the column on the right. Then choose an individual trace for a detailed summary.
 
 ![Detailed trace view]({{site.url}}{{site.baseurl}}/images/ta-trace.png)
 

_query-dsl/aggregations/pipeline-agg.md

@@ -5,6 +5,8 @@ parent: Aggregations
 nav_order: 5
 permalink: /aggregations/pipeline-agg/
 has_children: false
+redirect_from:
+  - /opensearch/pipeline-agg/
 ---
 
 # Pipeline aggregations

_search-plugins/index.md

@@ -11,7 +11,7 @@ nav_exclude: true
 
 OpenSearch provides several features for customizing your search use cases and improving search relevance. In OpenSearch, you can:
 
-- Use [SQL and Piped Processing Language (PPL)]({{site.url}}{{site.baseurl}}/search-plugins/sql/) as alternatives to [query domain-specific language (DSL)]({{site.url}}{{site.baseurl}}/query-dsl/) to search data.
+- Use [SQL and Piped Processing Language (PPL)]({{site.url}}{{site.baseurl}}/search-plugins/sql/index/) as alternatives to [query domain-specific language (DSL)]({{site.url}}{{site.baseurl}}/query-dsl/) to search data.
 
 - Run resource-intensive queries asynchronously with [asynchronous search]({{site.url}}{{site.baseurl}}/search-plugins/async/).
 
@@ -25,6 +25,6 @@ OpenSearch provides several features for customizing your search use cases and i
 
 - Use a dataset that is fixed in time to paginate results with [Point in Time]({{site.url}}{{site.baseurl}}/search-plugins/point-in-time/).
 
-- [Paginate]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/paginate) and [sort]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/sort/) search results, [highlight]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/highlight/) search terms, and use the [autocomplete]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/autocomplete/) and [did-you-mean]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/did-you-mean/) functionality.
+- [Paginate]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/paginate/) and [sort]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/sort/) search results, [highlight]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/highlight/) search terms, and use the [autocomplete]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/autocomplete/) and [did-you-mean]({{site.url}}{{site.baseurl}}/search-plugins/searching-data/did-you-mean/) functionality.
 
-- Rewrite queries with [Querqy]({{site.url}}{{site.baseurl}}/search-plugins/querqy).
+- Rewrite queries with [Querqy]({{site.url}}{{site.baseurl}}/search-plugins/querqy/).

_search-plugins/knn/jni-libraries.md

@@ -4,6 +4,8 @@ title: JNI libraries
 nav_order: 35
 parent: k-NN
 has_children: false
+redirect_from:
+ - /search-plugins/knn/jni-library/
 ---
 
 # JNI libraries

_search-plugins/sql/cli.md

@@ -3,6 +3,8 @@ layout: default
 title: SQL and PPL CLI
 parent: SQL and PPL
 nav_order: 3
+redirect_from:
+ - /search-plugins/sql/cli/
 ---
 
 # SQL and PPL CLI

_search-plugins/sql/index.md

@@ -5,7 +5,7 @@ nav_order: 38
 has_children: true
 has_toc: false
 redirect_from:
-  - /search-plugins/sql/
+  - /search-plugins/sql/index/
 ---
 
 # SQL and PPL

_search-plugins/sql/ppl/index.md

@@ -10,6 +10,8 @@ redirect_from:
   - /search-plugins/ppl/
   - /observability-plugin/ppl/
   - /search-plugins/ppl/index/
+  - /search-plugins/ppl/endpoint/
+  - /search-plugins/ppl/protocol/
 ---
 
 # PPL – Piped Processing Language

_search-plugins/sql/settings.md

@@ -7,7 +7,7 @@ redirect_from:
   - /search-plugins/sql/settings/
 ---
 
-# Settings
+# SQL settings
 
 The SQL plugin adds a few settings to the standard OpenSearch cluster settings. Most are dynamic, so you can change the default behavior of the plugin without restarting your cluster. 
 
@@ -75,6 +75,6 @@ Setting | Default | Description
 `plugins.sql.enabled` | True | Change to `false` to disable the `SQL` support in the plugin.
 `plugins.ppl.enabled` | True | Change to `false` to disable the `PPL` support in the plugin.
 `plugins.sql.slowlog` | 2 seconds | Configures the time limit (in seconds) for slow queries. The plugin logs slow queries as `Slow query: elapsed=xxx (ms)` in `opensearch.log`.
-`plugins.sql.cursor.keep_alive` | 1 minute | Configures how long the cursor context is kept open. Cursor contexts are resource resource intensive, so we recommend a low value.
+`plugins.sql.cursor.keep_alive` | 1 minute | Configures how long the cursor context is kept open. Cursor contexts are resource-intensive, so we recommend a low value.
 `plugins.query.memory_limit` | 85% | Configures the heap memory usage limit for the circuit breaker of the query engine.
 `plugins.query.size_limit` | 200 | Sets the default size of index that the query engine fetches from OpenSearch.

_security/access-control/cross-cluster-search.md

@@ -5,6 +5,7 @@ parent: Access control
 nav_order: 105
 redirect_from:
  - /security/access-control/cross-cluster-search/
+ - /security-plugin/access-control/cross-cluster-search/
 ---
 
 # Cross-cluster search

_security/access-control/default-action-groups.md

@@ -5,6 +5,7 @@ parent: Access control
 nav_order: 115
 redirect_from:
  - /security/access-control/default-action-groups/
+ - /security-plugin/access-control/default-action-groups/
 ---
 
 # Default action groups

_security/access-control/document-level-security.md

@@ -5,6 +5,7 @@ parent: Access control
 nav_order: 85
 redirect_from:
  - /security/access-control/document-level-security/
+ - /security-plugin/access-control/document-level-security/
 ---
 
 # Document-level security (DLS)

_security/access-control/field-level-security.md

@@ -5,6 +5,7 @@ parent: Access control
 nav_order: 90
 redirect_from:
  - /security/access-control/field-level-security/
+ - /security-plugin/access-control/field-level-security/
 ---
 
 # Field-level security

_security/access-control/field-masking.md

@@ -5,6 +5,7 @@ parent: Access control
 nav_order: 95
 redirect_from:
  - /security/access-control/field-masking/
+ - /security-plugin/access-control/field-masking/
 ---
 
 # Field masking

_security/access-control/impersonation.md

@@ -5,6 +5,7 @@ parent: Access control
 nav_order: 100
 redirect_from:
  - /security/access-control/impersonation/
+ - /security-plugin/access-control/impersonation/
 ---
 
 # User impersonation

_security/access-control/users-roles.md

@@ -5,6 +5,7 @@ parent: Access control
 nav_order: 80
 redirect_from:
  - /security/access-control/users-roles/
+ - /security-plugin/access-control/users-roles/
 ---
 
 # Users and roles

_security/audit-logs/field-reference.md

@@ -5,6 +5,7 @@ parent: Audit logs
 nav_order: 130
 redirect_from:
   - /security/audit-logs/field-reference/
+  - /security-plugin/audit-logs/field-reference/
 ---
 
 # Audit log field reference

_security/audit-logs/index.md

@@ -6,6 +6,7 @@ has_children: true
 has_toc: false
 redirect_from:
   - /security/audit-logs/index/
+  - /security-plugin/audit-logs/index/
 ---
 
 # Audit logs

_security/audit-logs/storage-types.md

@@ -5,6 +5,7 @@ parent: Audit logs
 nav_order: 135
 redirect_from:
   - /security/audit-logs/storage-types/
+  - /security-plugin/audit-logs/storage-types/
 ---
 
 # Audit log storage types

_security/configuration/configuration.md

@@ -3,6 +3,8 @@ layout: default
 title: Configuring the Security backend
 parent: Configuration
 nav_order: 5
+redirect_from:
+ - /security-plugin/configuration/configuration/
 ---
 
 # Configuring the Security backend

_security/configuration/system-indices.md

@@ -3,6 +3,8 @@ layout: default
 title: System indexes
 parent: Configuration
 nav_order: 4
+redirect_from:
+ - /security-plugin/configuration/system-indices/
 ---
 
 # System indexes

_tools/logstash/advanced-config.md

@@ -3,6 +3,8 @@ layout: default
 title: Advanced configurations
 parent: Logstash
 nav_order: 230
+redirect_from:
+ - /clients/logstash/advanced-config/
 ---
 
 # Advanced configurations
@@ -89,7 +91,7 @@ if EXPR {
 }
 ```
 
-`EXPR` is any valid Logstash syntax that evaluates to a boolean value.
+`EXPR` is any valid Logstash syntax that evaluates to a Boolean value.
 For example, you can check if an event type is set to `access` or `error` and perform some action based on that:
 
 ```yml
@@ -126,7 +128,7 @@ if [some_field] in ["one", "two", "three"] {
 }
 ```
 
-You can use boolean operators:
+You can use Boolean operators:
 
 ```yml
 if [type] == "access" or [type] == "error" {
@@ -235,7 +237,7 @@ geoip {
 
 Start Logstash and send an HTTP request.
 
-Within the terminal, you see a new field named `geoip` that contains information such as the time zone, country, continent, city, postal code, and the latitude / longitude pair.
+Within the terminal, you see a new field named `geoip` that contains information such as the time zone, country, continent, city, postal code, and the latitude/longitude pair.
 
 If you only need the country name for instance, include an option named `fields` with an array of the field names that you want the `geoip` plugin to return.
 

_tools/logstash/common-filters.md

@@ -3,6 +3,8 @@ layout: default
 title: Common filter plugins
 parent: Logstash
 nav_order: 220
+redirect_from:
+ - /clients/logstash/common-filters/
 ---
 
 # Common filter plugins

_tools/logstash/execution-model.md

@@ -3,6 +3,8 @@ layout: default
 title: Logstash execution model
 parent: Logstash
 nav_order: 210
+redirect_from:
+ - /clients/logstash/execution-model/
 ---
 
 # Logstash execution model
@@ -19,7 +21,7 @@ After receiving an event and possibly applying an input codec, Logstash sends th
 
 A pipeline worker consumes events from the work queue in batches to optimize the throughput of the pipeline as a whole.
 
-One reason why Logstash works in batches is that some code needs to be executed regardless of how many events are processed at a time within the pipeline worker. Instead of executing that code 100 times for 100 events, it’s more efficient to execute it once for a batch of 100 events.
+One reason why Logstash works in batches is that some code needs to be executed regardless of how many events are processed at a time within the pipeline worker. Instead of executing that code 100 times for 100 events, it’s more efficient to run it once for a batch of 100 events.
 
 Another reason is that a few output plugins group together events as batches. For example, if you send 100 requests to OpenSearch, the OpenSearch output plugin uses the bulk API to send a single request that groups together the 100 requests.
 

_tools/logstash/read-from-opensearch.md

@@ -3,6 +3,8 @@ layout: default
 title: Read from OpenSearch
 parent: Logstash
 nav_order: 220
+redirect_from:
+ - /clients/logstash/ship-to-opensearch/
 ---
 
 # Read from OpenSearch

_tools/logstash/ship-to-opensearch.md

@@ -3,6 +3,8 @@ layout: default
 title: Ship events to OpenSearch
 parent: Logstash
 nav_order: 220
+redirect_from:
+ - /clients/logstash/ship-to-opensearch/
 ---
 
 # Ship events to OpenSearch