Use mapped_pages instead of mapped_urls (#999)

When I was updating some mapped pages earlier, I noticed we were
inconsistently using `mapped_pages` and `mapped_urls`. It didn't matter
for the way I was finding the URLs, but I think it might affect how the
linking between old AsciiDoc pages and new pages works.

Author: colleenmcginnis

cloud-account/index.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-account-user-settings.html
   - https://www.elastic.co/guide/en/serverless/current/general-user-profile.html
 applies:
@@ -23,7 +23,7 @@ Additionally, you can manage your organization membership, including joining or
 
 Some options also let you set personal preferences and customize the interface, such as [using dark mode](dark-mode.md) in your projects and deployments.
 
-::::{tip} 
+::::{tip}
 This section focuses on the actions you can take as an individual user to manage your own account. It does not cover organization-wide settings, such as managing user permissions or configuring organization-level access controls, which are handled by the organization administrators.
 
 For information on organization and access management, refer to:

cloud-account/join-or-leave-an-organization.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-invite-users.html
   - https://www.elastic.co/guide/en/serverless/current/general-manage-organization.html
 applies:
@@ -35,7 +35,7 @@ If you already belong to an organization, and you want to join a new one you wil
 
 Alternatively, for Elastic Cloud Hosted deployments, there's a possibility to migrate your deployments to the new organization through back up and restore operations. In such case:
 
-1. [Back up your deployments to any private repository](/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md) so that you can restore them to your new organization. 
+1. [Back up your deployments to any private repository](/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md) so that you can restore them to your new organization.
 2. Leave your current organization.
 3. Ask the administrator to invite you to the organization you want to join.
 4. Accept the invitation that you will get by email.

deploy-manage/autoscaling.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-autoscaling.html
 applies_to:
   deployment:
@@ -19,7 +19,7 @@ By default, {{serverless-full}} automatically scales your {{es}} resources based
 
 ## Cluster autoscaling
 
-::::{admonition} Indirect use only 
+::::{admonition} Indirect use only
 This feature is designed for indirect use by {{ech}}, {{ece}}, and {{eck}}. Direct use is not supported.
 ::::
 
@@ -42,7 +42,7 @@ Trained model autoscaling automatically adjusts the resources allocated to train
 Trained model autoscaling supports:
 * Scaling trained model deployments
 
-::::{note} 
+::::{note}
 Autoscaling is not supported on Debian 8.
 ::::
 

deploy-manage/autoscaling/autoscaling-deciders.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/autoscaling-deciders.html
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/autoscaling-reactive-storage-decider.html
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/autoscaling-proactive-storage-decider.html

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-heroku/current/ech-autoscaling.html
   - https://www.elastic.co/guide/en/cloud/current/ec-autoscaling.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-autoscaling.html
@@ -200,7 +200,7 @@ The example deployment has a hot data and content tier, warm data tier, cold dat
 
 To learn more about the {{ece}} API, see the [RESTful API](cloud://reference/cloud-enterprise/restful-api.md) documentation. For details on the {{ech}} API, check [RESTful API](cloud://reference/cloud-hosted/ec-api-restful.md).
 
-### Requirements [ec_requirements] 
+### Requirements [ec_requirements]
 
 Note the following requirements when you run this API request:
 
@@ -218,7 +218,7 @@ Note the following requirements when you run this API request:
     * On all other components autoscaling is not currently supported.
 * On {{ece}}, autoscaling is supported for custom deployment templates on version 2.12 and above. To learn more, refer to [Updating custom templates to support `node_roles` and autoscaling](../deploy/cloud-enterprise/ce-add-support-for-node-roles-autoscaling.md).
 
-$$$ece-autoscaling-api-example-requirements-table$$$ 
+$$$ece-autoscaling-api-example-requirements-table$$$
 
 |  | `size` | `autoscaling_min` | `autoscaling_max` |
 | --- | --- | --- | --- |
@@ -237,7 +237,7 @@ $$$ece-autoscaling-api-example-requirements-table$$$
 
 ### API request example [ec_api_request_example]
 
-::::{note} 
+::::{note}
 Although autoscaling can scale some tiers by CPU, the primary measurement of tier size is memory. Limits on tier size are in terms of memory.
 ::::
 

deploy-manage/autoscaling/trained-model-autoscaling.md

@@ -1,13 +1,13 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/general-ml-nlp-auto-scale.html
   - https://www.elastic.co/guide/en/machine-learning/current/ml-nlp-auto-scale.html
 applies_to:
-  deployment: 
+  deployment:
     ess:
     eck:
     ece:
-  serverless: 
+  serverless:
 ---
 
 # Trained model autoscaling
@@ -93,7 +93,7 @@ On {{serverless-short}}, VCUs for {{ml}} are based on the amount of vCPU and mem
 As a math formula, `VCUs = 8 * allocations * threads`, or `1` VCU for every `1GB` of memory consumed, whichever is greater.
 ::::
 
-If you use a self-managed cluster or ECK, vCPUs level ranges are derived from the `total_ml_processors` and `max_single_ml_node_processors` values. Use the [get {{ml}} info API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-info) to check these values. 
+If you use a self-managed cluster or ECK, vCPUs level ranges are derived from the `total_ml_processors` and `max_single_ml_node_processors` values. Use the [get {{ml}} info API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-info) to check these values.
 
 The following tables show you the number of allocations, threads, and vCPUs available in ECE and ECH when adaptive resources are enabled or disabled.
 

deploy-manage/cloud-organization/billing.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-billing.html
   - https://www.elastic.co/guide/en/serverless/current/general-manage-billing.html
   - https://www.elastic.co/guide/en/serverless/current/general-billing-stop-project.html

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

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-billing-models.html
 applies_to:
   deployment:
@@ -17,7 +17,7 @@ You can be billed for {{ecloud}} using one of the following billing models:
 
 Regardless of your billing model, all {{ecloud}} usage is metered and billed in [Elastic Consumption Units (ECU)](/deploy-manage/cloud-organization/billing/ecu.md).
 
-## Monthly, billed by Elastic [ec-monthly-direct] 
+## Monthly, billed by Elastic [ec-monthly-direct]
 
 When you sign up for {{ecloud}} by [adding your credit card details](/deploy-manage/cloud-organization/billing/add-billing-details.md) in the {{ecloud}} Console, you are billed on a monthly basis.
 
@@ -27,19 +27,19 @@ All usage is expressed and charged in US dollars only.
 
 Refer to our [Billing FAQ](/deploy-manage/cloud-organization/billing/billing-faq.md) for more details about monthly invoicing.
 
-## Monthly, billed through a marketplace [ec-monthly-marketplace] 
+## Monthly, billed through a marketplace [ec-monthly-marketplace]
 
 You can sign up for {{ecloud}} [from a marketplace](/deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md). In this case, all usage is reported hourly to the marketplace.
 
 At the marketplace’s billing cycle, all usage is aggregated and charged as part of your cloud provider bill.
 
 {{ecloud}} usage appears as a single invoice line with the total amount charged. For a detailed breakdown of your usage, visit the [Usage page](/deploy-manage/cloud-organization/billing/monitor-analyze-usage.md) in the {{ecloud}} Console.
 
-::::{note} 
+::::{note}
 Marketplaces typically invoice you in arrears on the first of each month. There are exceptions, however, such as in the case of the [GCP billing cycle](https://cloud.google.com/billing/docs/how-to/billing-cycle).
 ::::
 
-## Prepaid consumption [ec-prepaid-consumption] 
+## Prepaid consumption [ec-prepaid-consumption]
 
 All new and renewing {{ecloud}} annual customers are automatically enrolled into the prepaid consumption billing model.
 
@@ -79,6 +79,6 @@ Based on these four key concepts, the prepaid consumption lifecycle is as follow
 
 ² Purchasing credits through early renewals, or through add-ons with different expiration dates will be available in the near future.
 
-::::{note} 
+::::{note}
 Existing annual+overages customers will be able to switch to prepaid consumption when they renew or sign a new contract. Existing manual burndown customers will be migrated gradually to prepaid consumption in the near future. Exceptions apply.
 ::::

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

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-billing-ecu.html
 applies_to:
   deployment:
@@ -15,7 +15,7 @@ The nominal value of one Elastic Consumption Unit is $1.00. You can use our [{{e
 
 Your monthly usage statement is issued in ECU, though it also includes the currency equivalent of your consumption. The **Usage** page in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) also shows usage information in ECU.
 
-## Contractual information and quoting [ec_contractual_information_and_quoting] 
+## Contractual information and quoting [ec_contractual_information_and_quoting]
 
 When you sign a prepaid consumption contract, you are purchasing Elastic Consumption Units which can be used to cover your {{ecloud}} usage throughout your contract period.
 

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

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/general-check-subscription.html
   - https://www.elastic.co/guide/en/cloud/current/ec-subscription-overview.html
   - https://www.elastic.co/guide/en/cloud/current/ec-select-subscription-level.html
@@ -13,14 +13,14 @@ applies_to:
 
 # Manage your subscription
 
-When you decide to add your credit card and become a paying customer, you can choose a subscription level. 
+When you decide to add your credit card and become a paying customer, you can choose a subscription level.
 
 Depending on whether you're using {{ech}} deployment or {{serverless-full}} projects, your subscription level might dictate what features you can access or what level of support you receive. On the following pricing pages, you can review additional details about what you get at each subscription level:
 
 * [{{ech}}](https://www.elastic.co/cloud/elasticsearch-service/pricing)
 * [{{serverless-full}}](https://www.elastic.co/pricing/serverless-search)
 
-You can find more details about your subscription in the [Billing overview page](https://cloud.elastic.co/billing/overview), in the **Subscription level** section. 
+You can find more details about your subscription in the [Billing overview page](https://cloud.elastic.co/billing/overview), in the **Subscription level** section.
 
 
 ## Change your subscription level [ec-select-subscription-level]

deploy-manage/cloud-organization/billing/monitor-analyze-usage.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-account-usage.html
   - https://www.elastic.co/guide/en/serverless/current/general-monitor-usage.html
 applies_to:
@@ -27,6 +27,6 @@ To access your account usage:
 3. Select **Billing** under the user menu.
 4. Go to the **Usage** page.
 
-::::{important} 
+::::{important}
 The usage breakdown information visible on the **Usage** page is an estimate, and does not include prepaid credits, free allowances or any discounts. To get the exact amount you owe for a given month, check your invoices in the [billing history](/deploy-manage/cloud-organization/billing/view-billing-history.md).
 ::::

deploy-manage/cloud-organization/billing/view-billing-history.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-billing-history.html
   - https://www.elastic.co/guide/en/serverless/current/general-billing-history.html
 applies_to:

deploy-manage/cloud-organization/service-status.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-service-status.html
   - https://www.elastic.co/guide/en/cloud/current/ec_subscribe_to_individual_regionscomponents.html
   - https://www.elastic.co/guide/en/cloud/current/ec_service_status_api.html
@@ -19,7 +19,7 @@ applies_to:
 
 To check current and past service availability, go to to the [Cloud Status](https://cloud-status.elastic.co/) page. Services are separated into {{ech}} services and [Serverless services](https://status.elastic.co/?section=serverless).
 
-## Subscribe to updates [ec_subscribe_to_updates] 
+## Subscribe to updates [ec_subscribe_to_updates]
 
 Don’t want to check the service status page manually? You can get notified about changes to the service status automatically.
 
@@ -36,7 +36,7 @@ After you subscribe to updates, you are notified whenever a service status updat
 
 ## Subscribe to individual regions or components
 
-If you want to know about specific status updates, rather than all of them, you can adjust your preferences by using the following steps. These steps apply to both new signups and adjustments to an existing subscription. 
+If you want to know about specific status updates, rather than all of them, you can adjust your preferences by using the following steps. These steps apply to both new signups and adjustments to an existing subscription.
 
 Go to the [Cloud Status](https://cloud-status.elastic.co/) page and select **SUBSCRIBE TO UPDATES**. Enter your email address and click **SUBSCRIBE VIA EMAIL**. You will be brought to a page with a list of regions and components.
 

deploy-manage/deploy.md

@@ -1,5 +1,5 @@
 ---
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/intro.html
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/elasticsearch-intro-deploy.html
   - https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/get-elastic.html

deploy-manage/deploy/cloud-enterprise.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/index.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/Elastic-Cloud-Enterprise-overview.html
 ---

deploy-manage/deploy/cloud-enterprise/air-gapped-install.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-install-offline.html
 ---
 

deploy-manage/deploy/cloud-enterprise/create-deployment.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-create-deployment.html
 ---
 

deploy-manage/deploy/cloud-enterprise/ece-integrations-server-api-example.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-integrations-server-api-example.html
 ---
 
@@ -13,14 +13,14 @@ This example demonstrates how to use the Elastic Cloud Enterprise RESTful API to
 For more information on how to manage Integrations Server from the UI, check [Manage your Integrations Server](manage-integrations-server.md)
 
 
-## Requirements [ece_requirements_4] 
+## Requirements [ece_requirements_4]
 
 Integrations Server can be enabled only on new deployments, starting with Elastic Stack version 8.0.
 
 It’s possible to enable Integrations Server on an existing deployment with version 8.0 only if [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-apm-and-fleet.html) hasn’t been previously enabled on the deployment.
 
 
-## API request example [ece_api_request_example_2] 
+## API request example [ece_api_request_example_2]
 
 Run this example API request to create a deployment with Integrations Server:
 

deploy-manage/deploy/cloud-enterprise/edit-stack-settings-apm.md

@@ -3,7 +3,7 @@ navigation_title: APM user settings
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-apm-settings.html
 ---
 

deploy-manage/deploy/cloud-enterprise/edit-stack-settings-elasticsearch.md

@@ -3,7 +3,7 @@ navigation_title: Elasticsearch user settings
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-add-user-settings.html
 ---
 

deploy-manage/deploy/cloud-enterprise/edit-stack-settings-enterprise.md

@@ -3,7 +3,7 @@ navigation_title: Enterprise search user settings
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-enterprise-search-settings.html
 ---
 

deploy-manage/deploy/cloud-enterprise/edit-stack-settings-kibana.md

@@ -3,7 +3,7 @@ navigation_title: Kibana user settings
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-kibana-settings.html
 ---
 

deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md

@@ -3,7 +3,7 @@ navigation_title: Edit stack settings
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/editing-user-settings.html
 ---
 

deploy-manage/deploy/cloud-enterprise/generate-roles-tokens.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-generate-roles-token.html
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-revoke-roles-token.html
 ---

deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: all
-mapped_urls:
+mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-integrations-server.html
 ---