Remove mailto: links

Author: bmorelli25

.gitignore

@@ -1,16 +1,2 @@
-# vscode stuff
-.vscode/*
-!.vscode/tasks.json
-
 # docs-builder default output
-.artifacts
-
-# vs stuff
-.vs/
-
-# osx stuff
-.DS_Store
-
-# jetbrains
-*.iml
-.idea
+.artifacts

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

@@ -68,7 +68,7 @@ $$$faq-payment$$$What are the available payment methods on Elasticsearch Service
 :   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]](mailto:[email protected]) or open a [Support case](../../../troubleshoot/troubleshoot/cloud.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/troubleshoot/cloud.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 our hosted Elasticsearch Service. 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.
@@ -149,7 +149,7 @@ $$$faq-on-demand$$$How can I pay for on-demand usage?
 :   We only support PO (invoicing) for on-demand usage, for prepaid consumption customers. The issued invoices include tax.
 
 $$$faq-lapse$$$What happens when a prepaid consumption contract expires and is not renewed?
-:   Your Elastic Cloud account will automatically change into a monthly account, paid through PO (invoicing). You will continue to incur costs, as we will not delete any of your deployments. You will not benefit from any discount because monthly customers are billed at list prices.  To switch your account to credit card payment, you must first send an email to [[email protected]](mailto:[email protected]) to indicate that this is your new preferred payment method. Once your email processed, Elastic will inform you that you can update your credit card information accordingly.
+:   Your Elastic Cloud account will automatically change into a monthly account, paid through PO (invoicing). You will continue to incur costs, as we will not delete any of your deployments. You will not benefit from any discount because monthly customers are billed at list prices.  To switch your account to credit card payment, you must first send an email to `[email protected]` to indicate that this is your new preferred payment method. Once your email processed, Elastic will inform you that you can update your credit card information accordingly.
 
 $$$faq-credits$$$If credits are purchased through multiple orders, which ones get used first?
 :   Credits get consumed in the order of expiration (first expired - first used). If two or more order lines have the same expiration date, the one with the highest discount is consumed first. If there are two or more order lines with the same discount, then the one with the lower balance is consumed first.

deploy-manage/deploy/elastic-cloud/aws-marketplace.md

@@ -55,7 +55,7 @@ To subscribe to Elasticsearch Service through the AWS Marketplace:
 
 ## Troubleshooting [ec-billing-aws-troubleshooting]
 
-This section describes some scenarios that you may experience onboarding onto the marketplace offer. If you’re running into issues with your marketplace subscription or are encountering technical issues, create a support case or contact [[email protected]](mailto:[email protected]).
+This section describes some scenarios that you may experience onboarding onto the marketplace offer. If you’re running into issues with your marketplace subscription or are encountering technical issues, create a support case or contact `[email protected]`.
 
 * [I receive an error message telling me that I’m already signed up using an Elastic Cloud email address.](#ec-awsmp-account-collision01)
 * [When I try to configure a new account from the AWS console, I get the Elastic Cloud login page, not the sign-up page. If I sign up to a new account it is not connected to the marketplace.](#ec-awsmp-account-collision02)
@@ -74,7 +74,7 @@ This occurs when you attempt to sign up to the marketplace offer using an email
 
 If the Elastic Cloud login page displays when coming from the AWS console, then an Elastic Cloud account is already connected to your marketplace subscription. Log into Elastic Cloud with that account to continue. If you can’t remember your password, use the **Forgot password?** link to reset your password.
 
-If you can’t remember which email address you used to sign up to Elastic Cloud, or you need more help, contact [[email protected]](mailto:[email protected]).
+If you can’t remember which email address you used to sign up to Elastic Cloud, or you need more help, contact `[email protected]`.
 
 
 ### When I try to configure an account from the AWS console I get an error that an active AWS subscription already exists. [ec-awsmp-account-collision03]

deploy-manage/deploy/elastic-cloud/azure-marketplace-pricing.md

@@ -10,12 +10,12 @@ The pricing in Azure Marketplace defines how on-demand usage and prepaid fees ge
 We will be updating the pricing plan for {{ecloud}} on Azure Marketplace effective January 1st, 2024. This update will affect customers paying in non-USD currencies.
 
 
-## Why we’re making these changes [ec_why_were_making_these_changes] 
+## Why we’re making these changes [ec_why_were_making_these_changes]
 
 The pricing plan update enables us to align with market trends and adapt to changing economic conditions, ensuring that we continue delivering the highest standard of service.
 
 
-## Who is affected [ec_who_is_affected] 
+## Who is affected [ec_who_is_affected]
 
 These pricing changes will apply to customers who are currently paying for Azure Marketplace services in non-USD currencies. If you are paying in USD, your pricing and billing will remain unchanged.
 
@@ -41,12 +41,11 @@ These pricing changes will apply to customers who are currently paying for Azure
 † used to avoid rounding issues: at list price, 1 ECU corresponds to 10,000 Elastic Billing Units for Azure
 
 
-## How the changes will affect you [ec_how_the_changes_will_affect_you] 
+## How the changes will affect you [ec_how_the_changes_will_affect_you]
 
 For customers paying in non-USD currencies, any future prepaid fees, or on-demand usage after the plan change will be charged at the new currency exchange rate. The applicable rate will be clearly displayed on the Azure Marketplace listing page, allowing you to stay informed about the pricing adjustments. You will receive an email from Azure Marketplace once the plan change is in effect.
 
 
-## Our commitment to you [ec_our_commitment_to_you] 
-
-We understand that pricing adjustments can raise questions or concerns, and we are here to support you throughout this process. Should you have any inquiries or need assistance, please reach out to your Elastic account representative or Elastic Support at [[email protected]](mailto:[email protected]).
+## Our commitment to you [ec_our_commitment_to_you]
 
+We understand that pricing adjustments can raise questions or concerns, and we are here to support you throughout this process. Should you have any inquiries or need assistance, please reach out to your Elastic account representative or Elastic Support at `[email protected]`.

deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md

@@ -182,7 +182,7 @@ $$$azure-integration-azure-rbac$$$Does {{ecloud}} Azure Native ISV Service suppo
 :   Yes. Currently [{{ecloud}} RBAC capability](../../users-roles/cloud-organization/user-roles.md) is available only from the {{ecloud}} Console and is not integrated with Azure Portal. This means that the users who will interact with Elastic resources from Azure Portal will not be recognized by the {{ecloud}} RBAC policies.
 
 $$$azure-integration-prior-cloud-account$$$I already have an {{ecloud}} account, can I use this service?
-:   Yes. If you already have an {{ecloud}} account with the same email address as your Azure account you may need to contact [[email protected]](mailto:[email protected]).
+:   Yes. If you already have an {{ecloud}} account with the same email address as your Azure account you may need to contact `[email protected]`.
 
 $$$azure-integration-convert-trial$$$Can I sign up for an {{ecloud}} trial account and then convert to the {{ecloud}} Azure Native ISV Service?
 :   Yes. You can start a [free Elasticsearch Service trial](https://cloud.elastic.co/registration?page=docs&placement=docs-body) and then convert your account over to Azure. There are a few requirements:
@@ -528,7 +528,7 @@ $$$azure-integration-support$$$How do I get support?
         :::
 
 
-    In case your {{ecloud}} resource is not fully set up and you’re not able to access the Support page, you can always send an email to [[email protected]](mailto:[email protected]).
+    In case your {{ecloud}} resource is not fully set up and you’re not able to access the Support page, you can always send an email to `[email protected]`.
 
 
 $$$azure-integration-change-level$$$How can I change my subscription level / support level?

deploy-manage/deploy/elastic-cloud/ech-get-help.md

@@ -8,13 +8,13 @@ mapped_pages:
 With your Elasticsearch Add-On for Heroku subscription, you get access to support from the creators of Elasticsearch, Kibana, Beats, Logstash, and much more. We’re here to help!
 
 
-## How do I open a support case? [echhow_do_i_open_a_support_case] 
+## How do I open a support case? [echhow_do_i_open_a_support_case]
 
 All roads lead to the Elastic Support Portal, where you can access to all your cases, subscriptions, and licenses.
 
-As an Elasticsearch Add-On for Heroku customer, you will receive an email with instructions how to log in to the Support Portal, where you can track both current and archived cases. If you are a new customer who just signed up for Elasticsearch Add-On for Heroku, it can take a few hours for your Support Portal access to be set up. If you have questions, reach out to us at [[email protected]](mailto:[email protected]).
+As an Elasticsearch Add-On for Heroku customer, you will receive an email with instructions how to log in to the Support Portal, where you can track both current and archived cases. If you are a new customer who just signed up for Elasticsearch Add-On for Heroku, it can take a few hours for your Support Portal access to be set up. If you have questions, reach out to us at `[email protected]`.
 
-::::{note} 
+::::{note}
 With the release of the new Support Portal, even if you have an existing account, you might be prompted to update your password.
 ::::
 
@@ -23,7 +23,7 @@ There are three ways you can get to the portal:
 
 * Go directly to the Support Portal: [http://support.elastic.co](http://support.elastic.co)
 * From the Elasticsearch Add-On for Heroku Console: Go to the [Support page](https://cloud.elastic.co/support?page=docs&placement=docs-body) or select the support icon, that looks like a life preserver, on any page in the console.
-* Contact us by email: [[email protected]](mailto:[email protected])
+* Contact us by email: `[email protected]`
 
     If you contact us by email, please use the email address that you registered with, so that we can help you more quickly. If you are using a distribution list as your registered email, you can also register a second email address with us. Just open a case to let us know the name and email address you would like to be added.
 
@@ -35,7 +35,7 @@ When opening a case, there are a few things you can do to get help faster:
 * Upload any pertinent files.
 
 
-## What level of support can I expect? [echwhat_level_of_support_can_i_expect] 
+## What level of support can I expect? [echwhat_level_of_support_can_i_expect]
 
 Support is governed by the [Elasticsearch Add-On for Heroku Standard Terms of Service](https://www.elastic.co/legal/terms-of-service/cloud). The level of support you can expect to receive applies to your Elasticsearch Add-On for Heroku environment only and depends on your subscription level:
 
@@ -45,22 +45,21 @@ Elasticsearch Add-On for Heroku Standard subscriptions
 Elasticsearch Add-On for Heroku Gold and Platinum subscriptions
 :   Support is handled by email or through the Elastic Support Portal. Provides guaranteed response times for support issues, better support coverage hours, and support contacts at Elastic. Also includes support for how-to and development questions. The exact support coverage depends on whether you are a Gold or Platinum customer. To learn more, check [Elasticsearch Add-On for Heroku Premium Support Services Policy](https://www.elastic.co/legal/support_policy/cloud_premium).
 
-::::{note} 
+::::{note}
 If you are in free trial, you are also eligible to get the Elasticsearch Service Standard level support for as long as the trial is active.
 ::::
 
 
 If you are on an Elasticsearch Add-On for Heroku Standard subscription and you are interested in moving to Gold or Platinum support, please [contact us](https://www.elastic.co/cloud/contact). We also recommend that you read our best practices guide for getting the most out of your support experience: [https://www.elastic.co/support/welcome](https://www.elastic.co/support/welcome).
 
 
-## Join the community forums [echjoin_the_community_forums] 
+## Join the community forums [echjoin_the_community_forums]
 
 Elasticsearch, Logstash, and Kibana enjoy the benefit of having vibrant and helpful communities. You have our assurance of high-quality support and single source of truth as an Elasticsearch Add-On for Heroku customer, but the Elastic community can also be a useful resource for you whenever you need it.
 
-::::{tip} 
+::::{tip}
 As of May 1, 2017, support for Elasticsearch Add-On for Heroku **Standard** customers has moved from the Discuss forum to our link: [Elastic Support Portal](https://support.elastic.co). You should receive login instructions by email. We will also monitor the forum and help you get into the Support Portal, in case you’re unsure where to go.
 ::::
 
 
 If you have any technical questions that are not for our Support team, hop on our [Elastic community forums](https://discuss.elastic.co/) and get answers from the experts in the community, including people from Elastic.
-

deploy-manage/deploy/elastic-cloud/ech-restrictions.md

@@ -124,10 +124,9 @@ To make a seamless migration, after restoring from a snapshot there are some add
 ## Known problems [ech-known-problems]
 
 * There is a known problem affecting clusters with versions 7.7.0 and 7.7.1 due to [a bug in Elasticsearch](https://github.com/elastic/elasticsearch/issues/56739). Although rare, this bug can prevent you from running plans. If this occurs we recommend that you retry the plan, and if that fails please contact support to get your plan through. Because of this bug we recommend you to upgrade to version 7.8 and higher, where the problem has already been addressed.
-* A known issue can prevent direct rolling upgrades from Elasticsearch version 5.6.10 to version 6.3.0. As a workaround, we have removed version 6.3.0 from the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) for new cluster deployments and for upgrading existing ones. If you are affected by this issue, check [Rolling upgrades from 5.6.x to 6.3.0 fails with "java.lang.IllegalStateException: commit doesn’t contain history uuid"](https://elastic.my.salesforce.com/articles/Support_Article/Rolling-upgrades-to-6-3-0-from-5-x-fails-with-java-lang-IllegalStateException-commit-doesn-t-contain-history-uuid?popup=false&id=kA0610000005JFG) in our Elastic Support Portal. If these steps do not work or you do not have access to the Support Portal, you can contact [[email protected]](mailto:[email protected]).
+* A known issue can prevent direct rolling upgrades from Elasticsearch version 5.6.10 to version 6.3.0. As a workaround, we have removed version 6.3.0 from the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) for new cluster deployments and for upgrading existing ones. If you are affected by this issue, check [Rolling upgrades from 5.6.x to 6.3.0 fails with "java.lang.IllegalStateException: commit doesn’t contain history uuid"](https://elastic.my.salesforce.com/articles/Support_Article/Rolling-upgrades-to-6-3-0-from-5-x-fails-with-java-lang-IllegalStateException-commit-doesn-t-contain-history-uuid?popup=false&id=kA0610000005JFG) in our Elastic Support Portal. If these steps do not work or you do not have access to the Support Portal, you can contact `[email protected]`.
 
 
 ## Repository Analysis API is unavailable in Elastic Cloud [ech-repository-analyis-unavailable]
 
 * The Elasticsearch [Repository analysis API](https://www.elastic.co/guide/en/elasticsearch/reference/current/repo-analysis-api.html) is not available in {{ecloud}} due to deployments defaulting to having [operator privileges](../../users-roles/cluster-or-deployment-auth/operator-privileges.md) enabled that prevent non-operator privileged users from using it along with a number of other APIs.
-

deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md

@@ -148,10 +148,9 @@ To make a seamless migration, after restoring from a snapshot there are some add
 ## Known problems [ec-known-problems]
 
 * There is a known problem affecting clusters with versions 7.7.0 and 7.7.1 due to [a bug in Elasticsearch](https://github.com/elastic/elasticsearch/issues/56739). Although rare, this bug can prevent you from running plans. If this occurs we recommend that you retry the plan, and if that fails please contact support to get your plan through. Because of this bug we recommend you to upgrade to version 7.8 and higher, where the problem has already been addressed.
-* A known issue can prevent direct rolling upgrades from Elasticsearch version 5.6.10 to version 6.3.0. As a workaround, we have removed version 6.3.0 from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) for new cluster deployments and for upgrading existing ones. If you are affected by this issue, check [Rolling upgrades from 5.6.x to 6.3.0 fails with "java.lang.IllegalStateException: commit doesn’t contain history uuid"](https://elastic.my.salesforce.com/articles/Support_Article/Rolling-upgrades-to-6-3-0-from-5-x-fails-with-java-lang-IllegalStateException-commit-doesn-t-contain-history-uuid?popup=false&id=kA0610000005JFG) in our Elastic Support Portal. If these steps do not work or you do not have access to the Support Portal, you can contact [[email protected]](mailto:[email protected]).
+* A known issue can prevent direct rolling upgrades from Elasticsearch version 5.6.10 to version 6.3.0. As a workaround, we have removed version 6.3.0 from the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) for new cluster deployments and for upgrading existing ones. If you are affected by this issue, check [Rolling upgrades from 5.6.x to 6.3.0 fails with "java.lang.IllegalStateException: commit doesn’t contain history uuid"](https://elastic.my.salesforce.com/articles/Support_Article/Rolling-upgrades-to-6-3-0-from-5-x-fails-with-java-lang-IllegalStateException-commit-doesn-t-contain-history-uuid?popup=false&id=kA0610000005JFG) in our Elastic Support Portal. If these steps do not work or you do not have access to the Support Portal, you can contact `[email protected]`.
 
 
 ## Repository Analysis API is unavailable in Elastic Cloud [ec-repository-analyis-unavailable]
 
 * The Elasticsearch [Repository analysis API](https://www.elastic.co/guide/en/elasticsearch/reference/current/repo-analysis-api.html) is not available in {{ecloud}} due to deployments defaulting to having [operator privileges](../../users-roles/cluster-or-deployment-auth/operator-privileges.md) enabled that prevent non-operator privileged users from using it along with a number of other APIs.
-