Fix home page and experimental feature warnings (#1206)

* Fix typos Signed-off-by: Naarcha-AWS <[email protected]> * Fix Dashboards link, place segment replication warnings under title, change remote from note to warning Signed-off-by: Naarcha-AWS <[email protected]> * Push index changes Signed-off-by: Naarcha-AWS <[email protected]> * Fix merge conflicts Signed-off-by: Naarcha-AWS <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
opensearch-project · Oct 6, 2022 · b18f2fe · b18f2fe
1 parent 7ade490
commit b18f2fe
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 7 deletions.
diff --git a/_opensearch/remote.md b/_opensearch/remote.md
@@ -6,10 +6,11 @@ nav_order: 19
 
 # Remote-backed storage
 
+Remote-backed storage is an experimental feature. Therefore, we do not recommend the use of remote-backed storage in a production environment. For updates on the progress of remote-backed storage, or if you want leave feedback that could help improve the feature, refer to the issue on [GitHub](https://github.com/opensearch-project/OpenSearch/issues/1968).
+{: .warning}
+
 Remote-backed storage offers OpenSearch users a new way to protect against data loss by automatically creating backups of all index transactions and sending them to remote storage. In order to expose this feature, segment replication must also be enabled. See [Segment replication]({{site.url}}{{site.baseurl}}/opensearch/segment-replication/) for additional information.
 
-Remote-backed storage is an experimental feature. Therefore, we do not recommend the use of remote-backed storage in a production environment. For updates on the progress of remote-backed storage, or if you want leave feedback that could help improve the feature, refer to the issue on [GitHub](https://github.com/opensearch-project/OpenSearch/issues/1968).
-{: .note}
 
 ## Enable the feature
 

diff --git a/_opensearch/segment-replication/configuration.md b/_opensearch/segment-replication/configuration.md
@@ -5,11 +5,11 @@ nav_order: 12
 parent: Segment replication
 ---
 
+# Segment replication configuration
+
 Segment replication is an experimental feature. Therefore, we do not recommend the use of segment replication in a production environment. For updates on the progress of segment replication or if you want to leave feedback that could help improve the feature, see the [Segment replication issue](https://github.com/opensearch-project/OpenSearch/issues/2229).
 {: .warning }
 
-# Segment replication configuration
-
 To enable the segment replication type, reference the steps below.
 
 ## Enabling the feature flag

diff --git a/_opensearch/segment-replication/index.md b/_opensearch/segment-replication/index.md
@@ -7,11 +7,11 @@ redirect_from:
   - /opensearch/segment-replication/
 ---
 
+# Segment replication
+
 Segment replication is an experimental feature with OpenSearch 2.3. Therefore, we do not recommend the use of segment replication in a production environment. For updates on the progress of segment replication or if you want leave feedback that could help improve the feature, see the [Segment replication git issue](https://github.com/opensearch-project/OpenSearch/issues/2229). 
 {: .warning}
 
-# Segment replication
-
 With segment replication, segment files are copied across shards instead of documents being indexed on each shard copy. This improves indexing throughput and lowers resource utilization at the expense of increased network utilization.
 
 As an experimental feature, segment replication will be behind a feature flag and must be enabled on **each node** of a cluster and pass a new setting during index creation.

diff --git a/index.md b/index.md
@@ -16,7 +16,7 @@ We have a dedicated and growing number of technical writers who are building our
 
 - [About OpenSearch]({{site.url}}{{site.baseurl}}/opensearch/)
 - [Install OpenSearch]({{site.url}}{{site.baseurl}}/opensearch/install/)
-- [Install OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/install/plugins/)
+- [Install OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/install/)
 - [See the FAQ](https://opensearch.org/faq)
 
 ## Why use OpenSearch?
@@ -29,6 +29,7 @@ With OpenSearch, you can perform the following use cases:
 Help users find the right information within your application, website, or data lake catalog. | Easily store and analyze log data, and set automated alerts for underperformance. | Centralize logs to enable real-time security monitoring and forensic analysis. | Use observability logs, metrics, and traces to monitor your applications and business in real time.
 
 
+
 **Additional features and plugins:**
 
 OpenSearch has several features and plugins to help index, secure, monitor, and analyze your data. Most OpenSearch plugins have corresponding OpenSearch Dashboards plugins that provide a convenient, unified user interface.