NO-JIRA: Mention properly an A record for external-dns with Hypershift

Author: mgencur

modules/hcp-aws-enable-ext-dns.adoc

@@ -30,7 +30,7 @@ However, when you deploy {hcp} in a managed service context, those methods can e
 
 When a DNS indirection is layered on the `LoadBalancer` and `Route` publishing types, a managed service operator can publish all public hosted cluster services by using a service-level domain. This architecture allows remapping on the DNS name to a new `LoadBalancer` or `Route` and does not expose the ingress domain of the management cluster. {hcp-capital} uses external DNS to achieve that indirection layer.
 
-You can deploy `external-dns` alongside the HyperShift Operator in the `hypershift` namespace of the management cluster. External DNS watches for `Services` or `Routes` that have the `external-dns.alpha.kubernetes.io/hostname` annotation. That annotation is used to create a DNS record that points to the `Service`, such as a record, or the `Route`, such as a CNAME record.
+You can deploy `external-dns` alongside the HyperShift Operator in the `hypershift` namespace of the management cluster. External DNS watches for `Services` or `Routes` that have the `external-dns.alpha.kubernetes.io/hostname` annotation. That annotation is used to create a DNS record that points to the `Service`, such as an A record, or the `Route`, such as a CNAME record.
 
 You can use external DNS on cloud environments only. For the other environments, you need to manually configure DNS and services.