fix(site): various broken url edits

src/content/docs/apis/intro-apis/new-relic-api-keys.mdx

@@ -52,7 +52,7 @@ Our keys can be broken down into two categories:
 
 There are many ways to [get data into New Relic](/docs/telemetry-data-platform/get-started/introduction-new-relic-data-ingest-apis-sdks). Here are the API keys used for data ingest: 
 
-* [License key](#ingest-license-key): our primary ingest key, used for APM ingest, infrastructure monitoring ingest, and our [ingest APIs](/docs/telemetry-data-platform/ingest-apis) and the integrations that use them. 
+* [License key](#ingest-license-key): our primary ingest key, used for APM ingest, infrastructure monitoring ingest, and our [ingest APIs](/docs/data-apis/ingest-apis) and the integrations that use them. 
 * [Browser key](#ingest-browser-key): used for browser monitoring ingest.
 * [Mobile app token](/docs/mobile-monitoring/new-relic-mobile/maintenance/viewing-your-application-token/): used for mobile monitoring ingest. 
 * [Insights insert key](#insights-insert-key): an older key that has been mostly deprecated, it has the same functionality as the license key. **We recommend using the license key instead.**

src/content/docs/apm/agents/c-sdk/instrumentation/instrument-transactions-c-sdk.mdx

@@ -6,6 +6,7 @@ metaDescription: >-
 redirects:
   - /docs/agents/c-sdk/instrumentation/instrument-transactions-c-sdk
   - /docs/instrument-transactions-c-agent
+  - /docs/instrument-transactions-c-sdk
 ---
 
 Instrument [transactions](/docs/apm/transactions/intro-transactions/transactions-new-relic-apm) using the C SDK so you can monitor any application on Linux that uses a language that can import C libraries. After you manually instrument transactions in your source code by adding New Relic functions, you can view the data on the [**Transactions** page](/docs/apm/applications-menu/monitoring/transactions-page) in the New Relic UI.

src/content/docs/apm/agents/c-sdk/instrumentation/instrument-your-app-c-sdk.mdx

@@ -10,6 +10,7 @@ metaDescription: 'How to instrument transactions, their segments, and errors in
 redirects:
   - /docs/agents/c-sdk/instrumentation/instrument-your-app-c-sdk
   - /docs/instrument-your-app-c-sdk
+  - /docs/instrument-segments-c-agent
 ---
 
 In order to monitor any application on Linux using a language that can import C libraries, you must:

src/content/docs/data-apis/ingest-apis/telemetry-sdks-report-custom-telemetry-data.mdx

@@ -16,7 +16,7 @@ redirects:
   - /docs/telemetry-data-platform/ingest-manage-data/ingest-apis/telemetry-sdks-report-custom-telemetry-data
 ---
 
-Our Telemetry SDKs are an open source set of API client libraries that send data to the New Relic platform. Under the hood, these SDKs rely on our core [data ingest APIs](/docs/telemetry-data-platform/ingest-apis): the Metric API, Trace API, Log API, and Event API.
+Our Telemetry SDKs are an open source set of API client libraries that send data to the New Relic platform. Under the hood, these SDKs rely on our core [data ingest APIs](/docs/data-apis/ingest-apis): the Metric API, Trace API, Log API, and Event API.
 
 We offer [open-source integrations](/docs/integrations/open-source-telemetry-integrations) for telemetry tools like Prometheus, Istio, and OpenCensus that were created using our Telemetry SDKs. If those solutions (or our other [integrations](https://newrelic.com/integrations)) don't meet your needs, you can use the Telemetry SDKs to create your own telemetry data solutions.
 

src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-cloudfront-monitoring-integration.mdx

@@ -31,7 +31,7 @@ You can change the polling frequency and filter data using [configuration option
 * New Relic polling interval: 5 minutes
 * Amazon CloudWatch data interval: [1 minute](http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/monitoring-using-cloudwatch.html), with up to 1 minute delay because CloudFront sometimes reports partial data
 
-If you're using [Lambda@Edge](mailto:Lambda@Edge) to customize content that CloudFront delivers so to execute Lambda functions in AWS locations closer to your clients, you can enable the **Collect [Lambda@Edge](mailto:Lambda@Edge) data** filter in order to get Lambda execution location metadata.
+If you're using Lambda@Edge to customize content that CloudFront delivers so to execute Lambda functions in AWS locations closer to your clients, you can enable the **Collect Lambda@Edge data** filter in order to get Lambda execution location metadata.
 
 ## Find and use data [#find-data]
 

src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration.mdx

@@ -116,7 +116,7 @@ Additionally, if you're using [AWS CloudFront](/docs/integrations/amazon-integra
       </td>
 
       <td>
-        The AWS region where the function is executed. Only for functions that are run by [Lambda@Edge](mailto:Lambda@Edge) service.
+        The AWS region where the function is executed. Only for functions that are run by Lambda@Edge service.
       </td>
     </tr>
 
@@ -338,7 +338,7 @@ This entity describes Lambda function inventory data. For full documentation on
       </td>
 
       <td>
-        For [Lambda@Edge](mailto:Lambda@Edge) functions, the ARN of the master function.
+        For Lambda@Edge functions, the ARN of the master function.
       </td>
     </tr>
 

src/content/docs/infrastructure/host-integrations/installation/update-infrastructure-host-integration-package.mdx

@@ -67,7 +67,7 @@ Use either of these options to check whether your infrastructure on-host integra
   </tbody>
 </table>
 
-To find the file name for a specific integration, see the [integration documentation](/docs/integrations/table-of-contents).
+To find the file name for a specific integration, see the [integration documentation](/docs/infrastructure/host-integrations).
 
 ## Update using apt (Debian or Ubuntu) [#apt]
 

src/content/docs/infrastructure/infrastructure-integrations/get-started/introduction-infrastructure-integrations.mdx

@@ -51,13 +51,13 @@ Cloud integrations collect data from cloud services and accounts. There's no ins
   <tbody>
     <tr id="aws-cloud">
       <td>
-        [Amazon Web Services (AWS) cloud-based integrations](/docs/integrations/amazon-integrations/aws-integrations-list)
+        [Amazon Web Services (AWS) cloud-based integrations](/docs/infrastructure/amazon-integrations/aws-integrations-list)
       </td>
 
       <td>
         Connect your Amazon Web Services (AWS) account to monitor and report data to New Relic.
 
-        See the list of [AWS integrations](/docs/integrations/amazon-integrations/aws-integrations-list).
+        See the list of [AWS integrations](/docs/infrastructure/amazon-integrations/aws-integrations-list).
       </td>
     </tr>
 

src/content/docs/new-relic-solutions/new-relic-solutions/optimize-your-cloud-native-environment/optimize-cloud-architecture-spend-continuously-improve-your-modern-cloud-environment.mdx

@@ -46,7 +46,7 @@ Make sure the following products and integrations are instrumented:
       </td>
 
       <td>
-        Instrument infrastructure: If you haven't already done so, review the requirements for the [Infrastructure agent](/docs/infrastructure). Infrastructure comes with several types of integrations, including [Amazon Web Services (AWS)](/docs/integrations/amazon-integrations/aws-integrations-list), [Microsoft Azure](/docs/integrations/microsoft-azure-integrations/azure-integrations-list), and [on-host integrations](/docs/integrations/host-integrations/host-integrations-list). After you've installed the Infrastructure agent on your host(s), you'll immediately have access to the broad spectrum of metrics the agent collects out-of-the-box.
+        Instrument infrastructure: If you haven't already done so, review the requirements for the [Infrastructure agent](/docs/infrastructure). Infrastructure comes with several types of integrations, including [Amazon Web Services (AWS)](/docs/infrastructure/amazon-integrations/aws-integrations-list), [Microsoft Azure](/docs/integrations/microsoft-azure-integrations/azure-integrations-list), and [on-host integrations](/docs/integrations/host-integrations/host-integrations-list). After you've installed the Infrastructure agent on your host(s), you'll immediately have access to the broad spectrum of metrics the agent collects out-of-the-box.
       </td>
     </tr>
 

src/content/docs/new-relic-solutions/new-relic-solutions/plan-your-cloud-adoption/optimize-your-cloud-spend.mdx

@@ -40,7 +40,7 @@ You may also want to include charts that represent the application using this cl
 
 ## 3. Configure the Amazon AWS integration [#configure-aws-integration]
 
-New Relic Infrastructure comes with several types of integrations, including [Amazon Web Services (AWS)](/docs/integrations/amazon-integrations/aws-integrations-list), [Microsoft Azure](/docs/integrations/microsoft-azure-integrations/azure-integrations-list), and [on-host integrations](/docs/integrations/host-integrations/host-integrations-list).
+New Relic Infrastructure comes with several types of integrations, including [Amazon Web Services (AWS)](/docs/infrastructure/amazon-integrations/aws-integrations-list), [Microsoft Azure](/docs/integrations/microsoft-azure-integrations/azure-integrations-list), and [on-host integrations](/docs/integrations/host-integrations/host-integrations-list).
 
 This tutorial focuses on the [AWS Billing integration](/docs/integrations/amazon-integrations/aws-integrations-list/aws-billing-monitoring-integration). First, [configure the integration](/docs/integrations/amazon-integrations/getting-started/connect-aws-services-infrastructure) with your AWS account, and then you can set up the AWS Billing integration.
 

src/content/docs/new-relic-solutions/new-relic-solutions/plan-your-cloud-adoption/refactor-your-applications.mdx

@@ -84,4 +84,4 @@ The following dashboard shows the MySQL request query latency as compared with a
   Use dashboards to visualize pre- and post-refactor baselines.
 </figcaption>
 
-With [APM agents](/docs/agents/manage-apm-agents/installation/install-agent) and the [integrations](/docs/integrations/table-of-contents) New Relic provides, you can measure the effectiveness of refactoring your applications using a broad spectrum of metrics.
+With [APM agents](/docs/agents/manage-apm-agents/installation/install-agent) and the other integrations New Relic provides, you can measure the effectiveness of refactoring your applications using a broad spectrum of metrics.

src/content/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/query-infrastructure-dimensional-metrics-nrql.mdx

@@ -66,7 +66,7 @@ For example, the query to get the maximum duration of your Lambda functions is s
 
 No agent or integration updates are required to use these metrics.
 
-[NRQL alerting](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) based on dimensional metrics is also supported, except for data coming from [cloud integrations](/docs/integrations/infrastructure-integrations/cloud-integrations) (that is metrics from [AWS polling integrations](/docs/integrations/amazon-integrations/aws-integrations-list), [GCP](/docs/integrations/google-cloud-platform-integrations), and [Azure](/docs/integrations/microsoft-azure-integrations/azure-integrations-list)). AWS CloudWatch Metric Streams metrics are ingested as dimensional metrics and NRQL alerts are recommended. 
+[NRQL alerting](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) based on dimensional metrics is also supported, except for data coming from [cloud integrations](/docs/integrations/infrastructure-integrations/cloud-integrations) (that is metrics from [AWS polling integrations](/docs/infrastructure/amazon-integrations/aws-integrations-list), [GCP](/docs/integrations/google-cloud-platform-integrations), and [Azure](/docs/integrations/microsoft-azure-integrations/azure-integrations-list)). AWS CloudWatch Metric Streams metrics are ingested as dimensional metrics and NRQL alerts are recommended. 
 
 ## Where and how to query dimensional metrics [#where]
 

src/content/docs/release-notes/infrastructure-release-notes/cloud-integration-release-notes/new-attributes-aws-services.mdx

@@ -8,7 +8,7 @@ redirects:
 
 ### New
 
-* If you're using [Lambda@Edge](https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html) to execute Lambda functions in AWS regions that are closer to your clients, you can get function execution location metadata by enabling the new **Collect [Lambda@Edge](mailto:Lambda@Edge) data** filter in the AWS CloudFront integration.
+* If you're using [Lambda@Edge](https://docs.aws.amazon.com/lambda/latest/dg/lambda-edge.html) to execute Lambda functions in AWS regions that are closer to your clients, you can get function execution location metadata by enabling the new **Collect Lambda@Edge data** filter in the AWS CloudFront integration.
 * The status of AWS VPC Network Interfaces and AWS VPC Peering Connections is now available, both as an inventory attribute (`status`) and as metrics metadata (`provider.status`).
 * The launch type of AWS ECS services is now available as an inventory attribute (`launchType`) and as metrics metadata (`provider.launchType`). It contains the type of infrastructure on which tasks and services are hosted (`EC2` or `FARGATE`).
 

src/content/docs/release-notes/infrastructure-release-notes/cloud-integration-release-notes/single-polling-interval.mdx

@@ -10,7 +10,7 @@ redirects:
 
 * In order to optimize the volume of calls to AWS APIs, the [cloud integrations setting](https://docs.newrelic.com/docs/integrations/new-relic-integrations/getting-started/configure-polling-frequency-data-collection-cloud-integrations) options have been enhanced. In particular:
   * New Relic will be using the same polling interval for metrics and inventory data from now on.
-  * Many options for you to control the amount of inventory data that New Relic collects from your cloud account have been added: tags, extended inventory, regions, entity name prefixes, resource groups, etc. Please find which attributes are fetched by enabling extended inventory in the specific document for [each cloud integration](https://docs.newrelic.com/docs/integrations/amazon-integrations/aws-integrations-list).
+  * Many options for you to control the amount of inventory data that New Relic collects from your cloud account have been added: tags, extended inventory, regions, entity name prefixes, resource groups, etc. Please find which attributes are fetched by enabling extended inventory in the specific document for [each cloud integration](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list).
 * You can enable or disable the collection of extended inventory attributes through New Relic's user interface for [AWS DynamoDB](https://docs.newrelic.com/docs/integrations/amazon-integrations/aws-integrations-list/aws-dynamodb-monitoring-integration), [AWS ElastiCache](https://docs.newrelic.com/docs/integrations/amazon-integrations/aws-integrations-list/aws-elasticache-monitoring-integration) and [Google Cloud BigQuery](https://docs.newrelic.com/docs/integrations/google-cloud-platform-integrations/gcp-integrations-list/google-bigquery-monitoring-integration).
 * The [AWS Lambda integration](https://docs.newrelic.com/docs/integrations/amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration) has been extended with additional metrics and inventory attributes:
   * The `ServerlessSample` event type now includes `deadLetterErrors` and `iteratorAge` metrics, both for functions and function aliases. Additionally, it includes the `concurrentExecutions` metric for functions that have a custom concurrency limit specified.

src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx

@@ -212,7 +212,7 @@ The following summarizes how individual New Relic products and components ensure
 
     The integration services are data agnostic. They will have no knowledge of whether the imported data contains any personal information. For more information, see the documentation for the specific integration, including:
 
-    * [Amazon Web Services (AWS)](/docs/integrations/amazon-integrations/aws-integrations-list)
+    * [Amazon Web Services (AWS)](/docs/infrastructure/amazon-integrations/aws-integrations-list)
     * [Google Cloud Platform (GCP)](/docs/integrations/google-cloud-platform-integrations/gcp-integrations-list)
     * [Kubernetes](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration)
     * [Microsoft Azure](/docs/integrations/microsoft-azure-integrations/azure-integrations-list)

src/content/docs/using-new-relic/welcome-new-relic/get-started/cloud-services-integrations.mdx

@@ -13,7 +13,7 @@ With New Relic you can easily instrument your services in AWS, Google Cloud Plat
 ## <ImageSizing width="64px" height="64px" verticalAlign="middle">![img-integration-aws@2x.png](./images/img-integration-aws%402x.png "img-integration-aws@2x.png")</ImageSizing> AWS integrations
 
 * [Introduction to AWS integrations](/docs/integrations/amazon-integrations/get-started/introduction-aws-integrations)
-* [List of AWS integrations](/docs/integrations/amazon-integrations/aws-integrations-list)
+* [List of AWS integrations](/docs/infrastructure/amazon-integrations/aws-integrations-list)
 
 ## <ImageSizing width="64px" height="64px" verticalAlign="middle">![img-integration-google@2x.png](./images/img-integration-google%402x.png "img-integration-google@2x.png")</ImageSizing> GCP integrations