Move misplaced Troubleshoot index (#456)

Use `mv` tool to move the Troubleshoot `index.md` file to the base
Troubleshoot directory instead of a subdirectory 🤦‍♀️

Author: marciw

cloud-account/multifactor-authentication.md

@@ -61,7 +61,7 @@ To enable multifactor authentication using an authenticator app, you must verify
 
 You can remove a multifactor authentication method after it’s added by clicking **Remove**.
 
-Before you remove an authentication method, you must set up an alternate method. If you can’t use any of your configured authentication methods — for example, if your device is lost or stolen — then [contact support](../troubleshoot/troubleshoot/index.md).
+Before you remove an authentication method, you must set up an alternate method. If you can’t use any of your configured authentication methods — for example, if your device is lost or stolen — then [contact support](../troubleshoot/index.md).
 
 
 ## Frequently asked questions [ec-account-security-mfa-faq]

deploy-manage/cloud-organization/billing/billing-faq.md

@@ -68,7 +68,7 @@ $$$faq-payment$$$What are the available payment methods on {{ecloud}}?
 :   For month-to-month payments only credit cards are accepted. We also allow payments by bank transfer for annual subscriptions.
 
 $$$faq-contact$$$Who can I contact for more information?
-:   If you have any further questions about your credit card statement, billing, or receipts, please send an email to `[email protected]` or open a [Support case](../../../troubleshoot/troubleshoot/index.md) using the *Billing issue* category.
+:   If you have any further questions about your credit card statement, billing, or receipts, please send an email to `[email protected]` or open a [Support case](../../../troubleshoot/index.md) using the *Billing issue* category.
 
 $$$faq-charge$$$Why is my credit card charged?
 :   If you are on a monthly plan, the charge is a recurring fee for using {{ecloud}}. The fee is normally charged at the start of each month, but it can also be charged at other times during the month. If a charge is unsuccessful, we will try to charge your card again at a later date.
@@ -86,10 +86,10 @@ $$$faq-chargednotusing$$$Why am I being charged if I don’t use any of my deplo
 :   Even if you have no activity on your account and you haven’t logged into the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), your active deployments still incur costs that we need to charge you for. To avoid being charged for active but unused deployments, you can simply delete them. Your account will stay active with no charges, and you can always spin up more capacity when you need it.
 
 $$$faq-deleteaccount$$$How can I delete my {{ecloud}} account?
-:   To have your account removed, you can contact support through the {{ecloud}} [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) or use one of these [alternative contact methods](../../../troubleshoot/troubleshoot/index.md). For details about our data erasure policy, check [Privacy Rights and Choices](https://www.elastic.co/legal/privacy-statement#privacy-rights-and-choices?page=docs&placement=docs-body) in our General Privacy Statement.
+:   To have your account removed, you can contact support through the {{ecloud}} [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) or use one of these [alternative contact methods](../../../troubleshoot/index.md). For details about our data erasure policy, check [Privacy Rights and Choices](https://www.elastic.co/legal/privacy-statement#privacy-rights-and-choices?page=docs&placement=docs-body) in our General Privacy Statement.
 
 $$$faq-refund$$$Can I get a refund?
-:   Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, please use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/troubleshoot/index.md).
+:   Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, please use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/index.md).
 
 $$$faq-included$$$What is included in my paid {{ech}} deployment?
 :   All subscription tiers for {{ech}} include the following free allowance:

raw-migrated-files/cloud/cloud/ec-about.md

@@ -7,6 +7,6 @@ The information in this section covers:
 * [Elasticsearch Service Hardware](https://www.elastic.co/guide/en/cloud/current/ec-reference-hardware.html)
 * [Elasticsearch Service Regions](https://www.elastic.co/guide/en/cloud/current/ec-reference-regions.html)
 * [Service Status](../../../deploy-manage/cloud-organization/service-status.md)
-* [Getting help](../../../troubleshoot/troubleshoot/index.md)
+* [Getting help](../../../troubleshoot/index.md)
 * [Restrictions and known problems](../../../deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md)
 

raw-migrated-files/cloud/cloud/ec-deployment-no-op.md

@@ -14,7 +14,7 @@ Re-saving the deployment configuration without making any changes is often all t
 
 **Seeing multiple warnings?**
 
-If multiple health warnings appear for one of your deployments, or if your deployment is unhealthy, we recommend [Getting help](../../../troubleshoot/troubleshoot/index.md) through the Elastic Support Portal.
+If multiple health warnings appear for one of your deployments, or if your deployment is unhealthy, we recommend [Getting help](../../../troubleshoot/index.md) through the Elastic Support Portal.
 
 **Warning about system changes**
 

raw-migrated-files/cloud/cloud/ec-faq-getting-started.md

@@ -34,7 +34,7 @@ This frequently-asked-questions list helps you with common questions while you g
     :   Scale your clusters both up and down from the user console, whenever you like. The resizing of the cluster is transparently done in the background, and highly available clusters are resized without any downtime. If you scale your cluster down, make sure that the downsized cluster can handle your {{es}} memory requirements. Read more about sizing and memory in [Sizing {{es}}](https://www.elastic.co/blog/found-sizing-elasticsearch).
 
     $$$faq-subscriptions$$$Do you offer support?
-    :   Yes, all subscription levels for Elasticsearch Service include support, handled by email or through the Elastic Support Portal. Different subscription levels include different levels of support. For the Standard subscription level, there is no service-level agreement (SLA) on support response times. Gold and Platinum subscription levels include an SLA on response times to tickets and dedicated resources. To learn more, check [Getting Help](../../../troubleshoot/troubleshoot/index.md).
+    :   Yes, all subscription levels for Elasticsearch Service include support, handled by email or through the Elastic Support Portal. Different subscription levels include different levels of support. For the Standard subscription level, there is no service-level agreement (SLA) on support response times. Gold and Platinum subscription levels include an SLA on response times to tickets and dedicated resources. To learn more, check [Getting Help](../../../troubleshoot/index.md).
 
     $$$faq-where$$$Where is Elasticsearch Service hosted?
     :   We host our {{es}} clusters on Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Check out which [regions we support](https://www.elastic.co/guide/en/cloud/current/ec-reference-regions.html) and what [hardware we use](https://www.elastic.co/guide/en/cloud/current/ec-reference-hardware.html). New data centers are added all the time.

raw-migrated-files/cloud/cloud/ec-monitoring.md

@@ -96,7 +96,7 @@ In a production environment, we highly recommend storing your logs and metrics i
 
 ## Dedicated logs and metrics [ec-es-health-dedicated]
 
-In a production environment, it’s important set up dedicated health monitoring in order to retain the logs and metrics that can be used to troubleshoot any health issues in your deployments. In the event of that you need to [contact our support team](../../../troubleshoot/troubleshoot/index.md), they can use the retained data to help diagnose any problems that you may encounter.
+In a production environment, it’s important set up dedicated health monitoring in order to retain the logs and metrics that can be used to troubleshoot any health issues in your deployments. In the event of that you need to [contact our support team](../../../troubleshoot/index.md), they can use the retained data to help diagnose any problems that you may encounter.
 
 You have the option of sending logs and metrics to a separate, specialized monitoring deployment, which ensures that they’re available in the event of a deployment outage. The monitoring deployment also gives you access to Kibana’s stack monitoring features, through which you can view health and performance data for all of your deployment resources.
 

raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md

@@ -22,7 +22,7 @@ If a cluster has unassigned shards, you might see an error message such as this
 :alt: Unhealthy deployment error message
 :::
 
-If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/index.md).
+If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/index.md).
 
 ## Analyze unassigned shards using the {{es}} API [ec-analyze_shards_with-api]
 
@@ -186,7 +186,7 @@ Here’s how to resolve the most common causes of unassigned shards reported by
 * [Maximum retry times exceeded](../../../troubleshoot/monitoring/unavailable-shards.md#ec-max-retry-exceeded)
 * [Max shard per node reached the limit](../../../troubleshoot/monitoring/unavailable-shards.md#ec-max-shard-per-node)
 
-If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/index.md).
+If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/index.md).
 
 ### Disk is full [ec-disk-full]
 

raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md

@@ -23,7 +23,7 @@ Some actions described here, such as stopping indexing or Machine Learning jobs,
 
 For production deployments, we recommend setting up a dedicated monitoring cluster to collect metrics and logs, troubleshooting views, and cluster alerts.
 
-If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/index.md).
+If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/index.md).
 
 ## Full disk on single-node deployment [ec-single-node-deployment-disk-used]
 
@@ -53,7 +53,7 @@ If your issue is not addressed here, then [contact Elastic support for help](../
 * Increase the disk size on your Hot data and Content tier (scale up).
 
 ::::{note}
-If your {{es}} cluster is unhealthy and reports a status of red, then increasing the disk size of your Hot data and Content tier may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/troubleshoot/index.md) and we will assist you with scaling up.
+If your {{es}} cluster is unhealthy and reports a status of red, then increasing the disk size of your Hot data and Content tier may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/index.md) and we will assist you with scaling up.
 ::::
 
 
@@ -100,7 +100,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, then increasing
 * Increase the disk size (scale up).
 
 ::::{note}
-If your {{es}} cluster is unhealthy and reports a status of red, the scale up configuration change to increasing disk size on the affected data tiers may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/troubleshoot/index.md) and we will assist you with scaling up.
+If your {{es}} cluster is unhealthy and reports a status of red, the scale up configuration change to increasing disk size on the affected data tiers may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/index.md) and we will assist you with scaling up.
 ::::
 
 

solutions/observability/unknown-bucket/serverless-observability-limitations.md

@@ -7,5 +7,5 @@ mapped_pages:
 
 Currently, the maximum ingestion rate for the Managed Intake Service (APM and OpenTelemetry ingest) is 11.5 MB/s of uncompressed data (roughly 1TB/d uncompressed equivalent). Ingestion at a higher rate may experience rate limiting or ingest failures.
 
-If you believe you are experiencing rate limiting or other ingest-based failures, please [contact Elastic Support](../../../troubleshoot/troubleshoot/index.md) for assistance.
+If you believe you are experiencing rate limiting or other ingest-based failures, please [contact Elastic Support](../../../troubleshoot/index.md) for assistance.