Merge pull request #1119 from himaatluri/patch-1

Update cross-account-access.adoc

Author: pgasca

latest/ug/manage-access/aws-access/cross-account-access.adoc

@@ -44,7 +44,7 @@ In this example, Account B creates an IAM policy with the permissions to give to
 [source,json,subs="verbatim,attributes"]
 ----
 {
-  "Version": "2012-10-17",&TCX5-2025-waiver;{tcx5-waiver}
+  "Version": "2012-10-17",{tcx5-waiver}
   "Statement": [
     {
       "Effect": "Allow",
@@ -63,7 +63,7 @@ Account A creates a role with a trust policy that gets credentials from the iden
 [source,json,subs="verbatim,attributes"]
 ----
 {
-  "Version": "2012-10-17",&TCX5-2025-waiver;{tcx5-waiver}
+  "Version": "2012-10-17",{tcx5-waiver}
   "Statement": [
     {
       "Effect": "Allow",
@@ -81,7 +81,7 @@ Account A attaches a policy to that role with the following permissions to assum
 [source,json,subs="verbatim,attributes"]
 ----
 {
-    "Version": "2012-10-17",&TCX5-2025-waiver;{tcx5-waiver}
+    "Version": "2012-10-17",{tcx5-waiver}
     "Statement": [
         {
             "Effect": "Allow",
@@ -107,4 +107,4 @@ role_arn={arn-aws}iam::111122223333:role/account-a-role
 
 To specify chained profiles for other {aws} SDKs, consult the documentation for the SDK that you're using. For more information, see link:developer/tools/[Tools to Build on {aws},type="marketing"].
 
-====
+====