Adjust text replacements for upstream patched-v4.54.0

Signed-off-by: Michael Bridgen <mbridgen@pulumi.com>

upstream-tools/pre-replacements.json

@@ -153,10 +153,6 @@
     }
   ],
   "website/docs/r/acmpca_certificate_authority.html.markdown": [
-    {
-      "old": "~> **NOTE:** Creating this resource will leave the certificate authority in a `PENDING_CERTIFICATE` status, which means it cannot yet issue certificates. To complete this setup, you must fully sign the certificate authority CSR available in the `certificate_signing_request` attribute and import the signed certificate outside of Terraform. Terraform can support another resource to manage that workflow automatically in the future.",
-      "new": "~> **NOTE:** Creating this resource will leave the certificate authority in a `PENDING_CERTIFICATE` status, which means it cannot yet issue certificates. To complete this setup, you must fully sign the certificate authority CSR available in the `certificate_signing_request` attribute and import the signed certificate using the AWS SDK, CLI or Console. This provider can support another resource to manage that workflow automatically in the future."
-    },
     {
       "old": "* `tags` - (Optional) Key-value map of user-defined tags that are attached to the certificate authority. If configured with a provider [`default_tags` configuration block](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#default_tags-configuration-block) present, tags with matching keys will overwrite those defined at the provider-level.",
       "new": "* `tags` - (Optional) Key-value map of user-defined tags that are attached to the certificate authority. If configured with a provider `default_tags` configuration block present, tags with matching keys will overwrite those defined at the provider-level."

upstream-tools/replacements.json

@@ -24,20 +24,12 @@
     }
   ],
   "website/docs/d/auditmanager_control.html.markdown": [
-    {
-      "old": "Terraform data source for managing an AWS Audit Manager Control.",
-      "new": "Data source for managing an AWS Audit Manager Control."
-    },
     {
       "old": "Terraform data source for managing an AWS Audit Manager Control.",
       "new": "Data source for managing an AWS Audit Manager Control."
     }
   ],
   "website/docs/d/auditmanager_framework.html.markdown": [
-    {
-      "old": "Terraform data source for managing an AWS Audit Manager Framework.",
-      "new": "Data source for managing an AWS Audit Manager Framework."
-    },
     {
       "old": "Terraform data source for managing an AWS Audit Manager Framework.",
       "new": "Data source for managing an AWS Audit Manager Framework."
@@ -468,20 +460,12 @@
     }
   ],
   "website/docs/r/auditmanager_framework_share.html.markdown": [
-    {
-      "old": "Terraform resource for managing an AWS Audit Manager Framework Share.",
-      "new": "Resource for managing an AWS Audit Manager Framework Share."
-    },
     {
       "old": "Terraform resource for managing an AWS Audit Manager Framework Share.",
       "new": "Resource for managing an AWS Audit Manager Framework Share."
     }
   ],
   "website/docs/r/auditmanager_organization_admin_account_registration.html.markdown": [
-    {
-      "old": "Terraform resource for managing AWS Audit Manager Organization Admin Account Registration.",
-      "new": "Resource for managing AWS Audit Manager Organization Admin Account Registration."
-    },
     {
       "old": "Terraform resource for managing AWS Audit Manager Organization Admin Account Registration.",
       "new": "Resource for managing AWS Audit Manager Organization Admin Account Registration."
@@ -1865,6 +1849,30 @@
       "new": "Resource for managing an AWS NetworkManager ConnectAttachment."
     }
   ],
+  "website/docs/r/networkmanager_core_network.html.markdown": [
+    {
+      "old": "* `create_base_policy` - (Optional) Specifies whether to create a base policy when a core network is created or updated. A base policy is created and set to `LIVE` to allow attachments to the core network (e.g. VPC Attachments) before applying a policy document provided using the `aws_networkmanager_core_network_policy_attachment` resource. This base policy is needed if your core network does not have any `LIVE` policies (e.g. a core network resource created without the `policy_document` argument) and your policy document has static routes pointing to VPC attachments and you want to attach your VPCs to the core network before applying the desired policy document. Valid values are `true` or `false`. Conflicts with `policy_document`. An example of this Terraform snippet can be found [above](#with-vpc-attachment). An example of a base policy created is shown below. The region specified in the `location` key can be configured using the `base_policy_region` argument. If `base_policy_region` is not specified, the region defaults to the region specified in the `provider` block. This base policy is overridden with the policy that you specify in the `aws_networkmanager_core_network_policy_attachment` resource.",
+      "new": "* `create_base_policy` - (Optional) Specifies whether to create a base policy when a core network is created or updated. A base policy is created and set to `LIVE` to allow attachments to the core network (e.g. VPC Attachments) before applying a policy document provided using the `aws_networkmanager_core_network_policy_attachment` resource. This base policy is needed if your core network does not have any `LIVE` policies (e.g. a core network resource created without the `policy_document` argument) and your policy document has static routes pointing to VPC attachments and you want to attach your VPCs to the core network before applying the desired policy document. Valid values are `true` or `false`. Conflicts with `policy_document`. An example of this snippet can be found [above](#with-vpc-attachment). An example of a base policy created is shown below. The region specified in the `location` key can be configured using the `base_policy_region` argument. If `base_policy_region` is not specified, the region defaults to the region specified in the `provider` block. This base policy is overridden with the policy that you specify in the `aws_networkmanager_core_network_policy_attachment` resource."
+    },
+    {
+      "old": "The example below illustrates the scenario where your policy document has static routes pointing to VPC attachments and you want to attach your VPCs to the core network before applying the desired policy document. Set the `create_base_policy` argument to `true` if your core network does not currently have any `LIVE` policies (e.g. this is the first `terraform apply` with the core network resource), since a `LIVE` policy is required before VPCs can be attached to the core network. Otherwise, if your core network already has a `LIVE` policy, you may exclude the `create_base_policy` argument.",
+      "new": "The example below illustrates the scenario where your policy document has static routes pointing to VPC attachments and you want to attach your VPCs to the core network before applying the desired policy document. Set the `create_base_policy` argument to `true` if your core network does not currently have any `LIVE` policies (e.g. this is the first `pulumi up` with the core network resource), since a `LIVE` policy is required before VPCs can be attached to the core network. Otherwise, if your core network already has a `LIVE` policy, you may exclude the `create_base_policy` argument."
+    },
+    {
+      "old": "~> **NOTE on Core Networks and Policy Attachments:** For a given core network, this resource's `policy_document` argument is incompatible with using the `aws_networkmanager_core_network_policy_attachment` resource. When using this resource's `policy_document` argument and the `aws_networkmanager_core_network_policy_attachment` resource, both will attempt to manage the core network's policy document and Terraform will show a permanent difference.",
+      "new": "~> **NOTE on Core Networks and Policy Attachments:** For a given core network, this resource's `policy_document` argument is incompatible with using the `aws_networkmanager_core_network_policy_attachment` resource. When using this resource's `policy_document` argument and the `aws_networkmanager_core_network_policy_attachment` resource, both will attempt to manage the core network's policy document and Pulumi will show a permanent difference."
+    }
+  ],
+  "website/docs/r/networkmanager_core_network_policy_attachment.html.markdown": [
+    {
+      "old": "The example below illustrates the scenario where your policy document has static routes pointing to VPC attachments and you want to attach your VPCs to the core network before applying the desired policy document. Set the `create_base_policy` argument of the `aws_networkmanager_core_network` resource to `true` if your core network does not currently have any `LIVE` policies (e.g. this is the first `terraform apply` with the core network resource), since a `LIVE` policy is required before VPCs can be attached to the core network. Otherwise, if your core network already has a `LIVE` policy, you may exclude the `create_base_policy` argument.",
+      "new": "The example below illustrates the scenario where your policy document has static routes pointing to VPC attachments and you want to attach your VPCs to the core network before applying the desired policy document. Set the `create_base_policy` argument of the `aws_networkmanager_core_network` resource to `true` if your core network does not currently have any `LIVE` policies (e.g. this is the first `pulumi up` with the core network resource), since a `LIVE` policy is required before VPCs can be attached to the core network. Otherwise, if your core network already has a `LIVE` policy, you may exclude the `create_base_policy` argument."
+    },
+    {
+      "old": "~> **NOTE on Core Networks and Policy Attachments:** For a given policy attachment, this resource is incompatible with using the `aws_networkmanager_core_network` resource `policy_document` argument. When using that argument and this resource, both will attempt to manage the core network's policy document and Terraform will show a permanent difference.",
+      "new": "~> **NOTE on Core Networks and Policy Attachments:** For a given policy attachment, this resource is incompatible with using the `aws_networkmanager_core_network` resource `policy_document` argument. When using that argument and this resource, both will attempt to manage the core network's policy document and Pulumi will show a permanent difference."
+    }
+  ],
   "website/docs/r/networkmanager_site_to_site_vpn_attachment.html.markdown": [
     {
       "old": "  Terraform resource for managing an AWS NetworkManager SiteToSiteAttachment.",
@@ -2042,10 +2050,6 @@
     }
   ],
   "website/docs/r/rds_export_task.html.markdown": [
-    {
-      "old": "Terraform resource for managing an AWS RDS (Relational Database) Export Task.",
-      "new": "Resource for managing an AWS RDS (Relational Database) Export Task."
-    },
     {
       "old": "Terraform resource for managing an AWS RDS (Relational Database) Export Task.",
       "new": "Resource for managing an AWS RDS (Relational Database) Export Task."
@@ -2684,6 +2688,12 @@
       "new": "~> **NOTE on VPC Endpoints and VPC Endpoint Security Group Associations:** The provider provides"
     }
   ],
+  "website/docs/r/vpc_ipam_pool_cidr.html.markdown": [
+    {
+      "old": "* `ipam_pool_cidr_id` - The unique ID generated by AWS for the pool cidr. Typically this is the resource `id` but this attribute was added to the API calls after the fact and is therefore not used as the terraform resource id.",
+      "new": "* `ipam_pool_cidr_id` - The unique ID generated by AWS for the pool cidr. Typically this is the resource `id` but this attribute was added to the API calls after the fact and is therefore not used as the resource id."
+    }
+  ],
   "website/docs/r/vpc_peering_connection.html.markdown": [
     {
       "old": "\n[1]: /docs/providers/aws/index.html"