Fix remaining links

Signed-off-by: Fanit Kolchina <[email protected]>

_about/quickstart.md

@@ -80,7 +80,7 @@ You'll need a special file, called a Compose file, that Docker Compose uses to d
 
 ## Create an index and field mappings using sample data
 
-Create an index and define field mappings using a dataset provided by the OpenSearch Project. The same fictitious e-commerce data is also used for sample visualizations in OpenSearch Dashboards. To learn more, see [Getting started with OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/get-started/quickstart-dashboards/).
+Create an index and define field mappings using a dataset provided by the OpenSearch Project. The same fictitious e-commerce data is also used for sample visualizations in OpenSearch Dashboards. 
 
 1. Download [ecommerce-field_mappings.json](https://github.com/opensearch-project/documentation-website/blob/{{site.opensearch_major_minor_version}}/assets/examples/ecommerce-field_mappings.json). This file defines a [mapping]({{site.url}}{{site.baseurl}}/opensearch/mappings/) for the sample data you will use.
     ```bash
@@ -132,8 +132,7 @@ You successfully deployed your own OpenSearch cluster with OpenSearch Dashboards
 - [About the security plugin]({{site.url}}{{site.baseurl}}/security/index/)
 - [OpenSearch configuration]({{site.url}}{{site.baseurl}}/install-and-configure/configuration/)
 - [OpenSearch plugin installation]({{site.url}}{{site.baseurl}}/opensearch/install/plugins/)
-- [Getting started with OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/get-started/quickstart-dashboards/)
-- [OpenSearch tools]({{site.url}}{{site.baseurl}}/tools/index/)
+- [OpenSearch tools]({{site.url}}{{site.baseurl}}/clients/agents-and-ingestion-tools/index/)
 - [Index APIs]({{site.url}}{{site.baseurl}}/api-reference/index-apis/index/)
 
 ## Common issues

_api-reference/script-apis/create-stored-script.md

@@ -13,7 +13,7 @@ For additional information about Painless scripting, see:
 
 * [k-NN Painless Scripting extensions]({{site.url}}{{site.baseurl}}/search-plugins/knn/painless-functions/).
 
-* [k-NN]({{site.url}}{{site.baseurl}}/search-plugins/knn/inswz/).
+* [k-NN]({{site.url}}{{site.baseurl}}/search-plugins/knn/index/).
 
 
 ### Path parameters

_clients/logstash/ship-to-opensearch.md

@@ -9,7 +9,7 @@ nav_order: 220
 
 You can Ship Logstash events to an OpenSearch cluster and then visualize your events with OpenSearch Dashboards.
 
-Make sure you have [Logstash]({{site.url}}{{site.baseurl}}/tools/logstash/index#install-logstash), [OpenSearch]({{site.url}}{{site.baseurl}}/install-and-configure/install-opensearch/index/), and [OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/install-and-configure/install-dashboards/index/).
+Make sure you have [Logstash]({{site.url}}{{site.baseurl}}/clients/logstash/index#install-logstash), [OpenSearch]({{site.url}}{{site.baseurl}}/install-and-configure/install-opensearch/index/), and [OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/install-and-configure/install-dashboards/index/).
 {: .note }
 
 ## OpenSearch output plugin

_dashboards/discover/index-discover.md

@@ -17,7 +17,7 @@ has_children: true
 
 This tutorial shows you how to use Discover to analyze and understand a sample dataset. At the end of this tutorial, you should be ready to use Discover with your own data.
 
-Before starting this tutorial, make sure you've added the **Sample flight data**. See [Quickstart guide for OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/get-started/quickstart-dashboards/) for information about how to get started.
+Before starting this tutorial, make sure you've added the **Sample flight data**. 
 {: .warning}
 
 ### Setting up data

_dashboards/visualize/viz-index.md

@@ -65,7 +65,7 @@ Line charts compare changes in measured values over a period of time, such as gr
 
 ### Maps
 
-You can create two types of maps in Dashboards: Coordinate maps and Region maps. Coordinate maps show the difference between data values for each location by size. Region maps show the difference between data values for each location by varying shades of color. See [Using the Maps plugin]({{site.url}}{{site.baseurl}}/dashboards/maps-plugin/) to learn more about maps capabilities in Dashboards.
+You can create two types of maps in Dashboards: Coordinate maps and Region maps. Coordinate maps show the difference between data values for each location by size. Region maps show the difference between data values for each location by varying shades of color. 
 
 #### Coordinate maps
 

_install-and-configure/upgrade-opensearch/appendix/rolling-upgrade-lab.md

@@ -887,6 +887,5 @@ You need to query the ecommerce index again in order to confirm that the sample
 Review the following resoures to learn more about how OpenSearch works:
 
 - [REST API reference]({{site.url}}{{site.baseurl}}/api-reference/index/)
-- [Quickstart guide for OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/get-started/quickstart-dashboards/)
 - [About Security in OpenSearch]({{site.url}}{{site.baseurl}}/security/index/)
 

_install-and-configure/upgrade-opensearch/index.md

@@ -43,7 +43,7 @@ It's important to determine how the new version of OpenSearch will integreate wi
 
 ### Reviewing the OpenSearch tools compatibility matrices
 
-If your OpenSearch cluster interacts with other services in your environment, like Logstash or Beats, then you should check the [OpenSearch tools compatibility matrices]({{site.url}}{{site.baseurl}}/tools/index/#compatibility-matrices) to determine whether other components will need to be upgraded.
+If your OpenSearch cluster interacts with other services in your environment, like Logstash or Beats, then you should check the [OpenSearch tools compatibility matrices]({{site.url}}{{site.baseurl}}/clients/agents-and-ingestion-tools/index/#compatibility-matrices) to determine whether other components will need to be upgraded.
 
 ### Reviewing plugin compatibility
 

_observing-your-data/log-ingestion.md

@@ -12,7 +12,7 @@ Log ingestion provides a way to transform unstructured log data into structured
 
 ## Get started with log ingestion
 
-OpenSearch Log Ingestion consists of three components---[Data Prepper]({{site.url}}{{site.baseurl}}/clients/data-prepper/index/), [OpenSearch]({{site.url}}{{site.baseurl}}/quickstart/), and [OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/get-started/quickstart-dashboards/). The Data Prepper repository contains several [sample applications](https://github.com/opensearch-project/data-prepper/tree/main/examples) that you can use to get started.
+OpenSearch Log Ingestion consists of three components---[Data Prepper]({{site.url}}{{site.baseurl}}/clients/data-prepper/index/) and [OpenSearch]({{site.url}}{{site.baseurl}}/quickstart/). The Data Prepper repository contains several [sample applications](https://github.com/opensearch-project/data-prepper/tree/main/examples) that you can use to get started.
 
 ### Basic flow of data
 

_opensearch/ux.md

@@ -39,7 +39,7 @@ These methods are described in the following sections.
 Prefix matching finds documents that matches the last term in the query string.
 
 For example, assume that the user types “qui” into a search UI. To autocomplete this phrase, use the `match_phrase_prefix` query to search all `text_entry` fields that begin with the prefix "qui."
-To make the word order and relative positions flexible, specify a `slop` value. To learn about the `slop` option, see the [Multi-match query]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text#multi-match).
+To make the word order and relative positions flexible, specify a `slop` value. To learn about the `slop` option, see the [Multi-match query]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/index/#multi-match).
 
 #### Sample Request
 
@@ -60,7 +60,7 @@ GET shakespeare/_search
 Prefix matching doesn’t require any special mappings. It works with your data as-is.
 However, it’s a fairly resource-intensive operation. A prefix of `a` could match hundreds of thousands of terms and not be useful to your user.
 
-To limit the impact of prefix expansion, set `max_expansions` to a reasonable number. To learn about the `max_expansions` option, see [Advanced filter options]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text#advanced-filter-options).
+To limit the impact of prefix expansion, set `max_expansions` to a reasonable number. To learn about the `max_expansions` option, see [Advanced filter options]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/index/#advanced-filter-options).
 
 #### Sample Request
 

_plugins/link-checker.rb

@@ -247,6 +247,7 @@ def self.check_external(url, location)
 
   def self.check_internal(url, location)
     Jekyll.logger.info "LinkChecker: [Info] Checking #{url}".cyan
+    Jekyll.logger.info "LinkChecker: [Info] Checking #{url} (#{location})".cyan
     return true if @ignored_paths =~ url
 
     path, hash = url.split('#')

_tuning-your-cluster/availability-and-recovery/snapshots/sm-api.md

@@ -185,7 +185,7 @@ Parameter | Type | Description
 `snapshot_config`<br>&nbsp;&nbsp;&nbsp;&nbsp;`indices` | String | The names of the indexes in the snapshot. Multiple index names are separated by `,`. Supports wildcards (`*`). Optional. Default is `*` (all indexes).
 `snapshot_config`<br>&nbsp;&nbsp;&nbsp;&nbsp;`repository` | String | The repository in which to store snapshots. Required.
 `snapshot_config`<br>&nbsp;&nbsp;&nbsp;&nbsp;`ignore_unavailable` | Boolean | Do you want to ignore unavailable indexes? Optional. Default is `false`.
-`snapshot_config`<br>&nbsp;&nbsp;&nbsp;&nbsp;`include_global_state` | Boolean | Do you want to include cluster state? Optional. Default is `true` because of [Security plugin considerations]({{site.url}}{{site.baseurl}}/opensearch/snapshots/snapshot-restore/#security-plugin-considerations).
+`snapshot_config`<br>&nbsp;&nbsp;&nbsp;&nbsp;`include_global_state` | Boolean | Do you want to include cluster state? Optional. Default is `true` because of [Security plugin considerations]({{site.url}}{{site.baseurl}}/opensearch/snapshots/snapshot-restore/#security-considerations).
 `snapshot_config`<br>&nbsp;&nbsp;&nbsp;&nbsp;`partial` | Boolean | Do you want to allow partial snapshots? Optional. Default is `false`.
 `snapshot_config`<br>&nbsp;&nbsp;&nbsp;&nbsp;`metadata` | Object | Metadata in the form of key/value pairs. Optional.
 `creation` | Object | Configuration for snapshot creation. Required.