fix carats at end of code line

consistency-groups/configure-hierarchy-task.adoc

@@ -53,7 +53,7 @@ When creating a hierarchical consistency group in the CLI with new volumes, you
 .Step
 . Create the new consistency group using the `consistency-group create` command. 
 +
-`consistency-group create -vserver <SVM_name_ -consistency-group <consistency_group_name_ -parent-consistency-group <parent_consistency_group_name_ -volume-prefix <volume_prefix_ -volume-count <number_of_volumes_ -size <size_`
+`consistency-group create -vserver <SVM_name> -consistency-group <consistency_group_name> -parent-consistency-group <parent_consistency_group_name> -volume-prefix <volume_prefix> -volume-count <number_of_volumes> -size <size>`
 . When prompted by the CLI, confirm you want to create the new parent consistency group. Enter `y`. 
 . Optionally, repeat step 1 to create more child consistency groups.
 --
@@ -90,7 +90,7 @@ include::../_include/consistency-group-cli.adoc[]
 .Steps
 . Provision a new parent consistency group and assign volumes to a new child consistency group:
 +
-`consistency-group create -vserver <svm_name_ -consistency-group <child_consistency_group_name_ -parent-consistency-group <parent_consistency_group_name_ -volumes <volume_names_`
+`consistency-group create -vserver <svm_name> -consistency-group <child_consistency_group_name> -parent-consistency-group <parent_consistency_group_name> -volumes <volume_names>`
 . Enter `y` to confirm you want to create a new parent and child consistency group.
 --
 ====

consistency-groups/configure-task.adoc

@@ -48,17 +48,17 @@ include::../_include/consistency-group-cli.adoc[]
 .Create a consistency group with NFS volumes
 . Create the consistency group:
 +
-`consistency-group create -vserver <SVM_name> -consistency-group <consistency-group-name> -volume-prefix <prefix_for_new_volume_names> -volume-count <number> -size <size> -export-policy <policy_name_`
+`consistency-group create -vserver <SVM_name> -consistency-group <consistency-group-name> -volume-prefix <prefix_for_new_volume_names> -volume-count <number> -size <size> -export-policy <policy_name>`
 
 .Create a consistency group with SAN volumes
 . Create the consistency group:
 +
-`consistency-group create -vserver <SVM_name> -consistency-group <consistency-group-name> -lun <lun_name> -size <size> -lun-count <number> -lun-os-type <LUN_operating_system_format> -igroup <igroup_name_`
+`consistency-group create -vserver <SVM_name> -consistency-group <consistency-group-name> -lun <lun_name> -size <size> -lun-count <number> -lun-os-type <LUN_operating_system_format> -igroup <igroup_name>`
 
 .Create a consistency group with NVMe namespaces
 . Create the consistency group:
 +
-`consistency-group create -vserver <SVM_name> -consistency-group <consistency_group_name> -namespace <namespace_name> -volume-count <number> -namespace-count <number> -size <size> -subsystem <subsystem_name_`
+`consistency-group create -vserver <SVM_name> -consistency-group <consistency_group_name> -namespace <namespace_name> -volume-count <number> -namespace-count <number> -size <size> -subsystem <subsystem_name>`
 
 .After you're done
 . Confirm your consistency group has been created using the `consistency-group show` command. 
@@ -98,7 +98,7 @@ include::../_include/consistency-group-cli.adoc[]
 .Steps
 . Issue the `consistency-group create` command. The `-volumes` parameter accepts a comma-separated list of volume names.
 +
-`consistency-group create -vserver <SVM_name> -consistency-group <consistency-group-name> -volume <volumes_`
+`consistency-group create -vserver <SVM_name> -consistency-group <consistency-group-name> -volume <volumes>`
 . View your consistency group using the `consistency-group show` command. 
 --
 ====

snapmirror-active-sync/interoperability-reference.adoc

@@ -108,7 +108,7 @@ For ONTAP Releases 9.12.1P2 and later, you must ensure that both the primary and
 
 .ONTAP 9.9.1 - 9.12.1P1
 --
-* For ONTAP releases between ONTAP 9.9.1 and 9.12.1 P1 (inclusive), Large LUNs and large volumes greater than 100TB are supported only on All-Flash SAN Arrays.
+* For ONTAP releases between ONTAP 9.9.1 and 9.12.1 P1 (inclusive), Large LUNs and large volumes greater than 100TB are supported only on All-Flash SAN Arrays. Replication from AFF A-Series to AFF C-Series and vice versa is supported.
 
 [NOTE]
 For ONTAP releases between ONTAP 9.9.1 and 9.12.1 P2, you must ensure that both the primary and secondary clusters are All-Flash SAN Arrays, and that they both have ONTAP 9.9.1 or later installed. If the secondary cluster is running a version earlier than ONTAP 9.9.1 or if it is not an All-Flash SAN Array, the synchronous relationship can go out of sync if the primary volume grows larger than 100 TB.