A tiny change in HCP release notes structure

Author: xenolinux

hosted_control_planes/hosted-control-planes-release-notes.adoc

@@ -8,47 +8,50 @@ toc::[]
 
 Release notes contain information about new and deprecated features, changes, and known issues.
 
+[id="hcp-4-17-release-notes_{context}"]
+== {hcp-capital} release notes for {product-title} 4.17
+
 With this release, {hcp} for {product-title} 4.17 is available. {hcp-capital} for {product-title} 4.17 supports the {mce} version 2.7.
 
 [id="hcp-4-17-new-features-and-enhancements_{context}"]
-== New features and enhancements
+=== New features and enhancements
 
 This release adds improvements related to the following concepts:
 
 [id="hcp-4-17-taints-tolerations_{context}"]
-=== Custom taints and tolerations (Technology Preview)
+==== Custom taints and tolerations (Technology Preview)
 For {hcp} on {VirtProductName}, you can now apply tolerations to hosted control plane pods by using the `hcp` CLI `-tolerations` argument or by using the `hc.Spec.Tolerations` API file. This feature is available as a Technology Preview feature. For more information, see xref:../hosted_control_planes/hcp-prepare/hcp-distribute-workloads.adoc#hcp-virt-taints-tolerations_hcp-distribute-workloads[Custom taints and tolerations].
 
 [id="hcp-4-17-nvidia-gpu_{context}"]
-=== Support for NVIDIA GPU devices on {VirtProductName} (Technology Preview)
+==== Support for NVIDIA GPU devices on {VirtProductName} (Technology Preview)
 For {hcp} on {VirtProductName}, you can attach one or more NVIDIA graphics processing unit (GPU) devices to node pools. This feature is available as a Technology Preview feature. For more information, see xref:../hosted_control_planes/hcp-manage/hcp-manage-virt.adoc#hcp-virt-attach-nvidia-gpus_hcp-manage-virt[Attaching NVIDIA GPU devices by using the hcp CLI] and xref:../hosted_control_planes/hcp-manage/hcp-manage-virt.adoc#hcp-virt-attach-nvidia-gpus-np-api_hcp-manage-virt[Attaching NVIDIA GPU devices by using the NodePool resource].
 
 [id="hcp-4-17-tenancy-aws_{context}"]
-=== Support for tenancy on {aws-short}
+==== Support for tenancy on {aws-short}
 When you create a hosted cluster on {aws-short}, you can indicate whether the EC2 instance should run on shared or single-tenant hardware. For more information, see xref:../hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc#hcp-aws-deploy-hc_hcp-deploy-aws[Creating a hosted cluster on {aws-short}].
 
 [id="hcp-4-17-ocp-version-support_{context}"]
-=== Support for {product-title} versions in hosted clusters
+==== Support for {product-title} versions in hosted clusters
 You can deploy a range of supported {product-title} versions in a hosted cluster. For more information, see xref:../hosted_control_planes/hcp-updating.adoc#hcp-supported-ocp-versions_hcp-updating[Supported {product-title} versions in a hosted cluster].
 
 [id="hcp-4-17-virt-dc_{context}"]
-=== {hcp-capital} on {VirtProductName} in a disconnected environment is Generally Available
+==== {hcp-capital} on {VirtProductName} in a disconnected environment is Generally Available
 In this release, {hcp} on {VirtProductName} in a disconnected environment is Generally Available. For more information, see xref:../hosted_control_planes/hcp-disconnected/hcp-deploy-dc-virt.adoc[Deploying {hcp} on {VirtProductName} in a disconnected environment].
 
 [id="hcp-4-17-multi_{context}"]
-=== {hcp-capital} for an ARM64 {product-title} cluster on {aws-short} is Generally Available
+==== {hcp-capital} for an ARM64 {product-title} cluster on {aws-short} is Generally Available
 In this release, {hcp} for an ARM64 {product-title} cluster on {aws-short} is Generally Available. For more information, see xref:../hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc#hcp-enable-arm-amd_hcp-deploy-aws[Running hosted clusters on an ARM64 architecture].
 
 [id="hcp-4-17-ibm-z-ga_{context}"]
-=== {hcp-capital} on {ibm-z-title} is Generally Available
+==== {hcp-capital} on {ibm-z-title} is Generally Available
 In this release, {hcp} on {ibm-z-title} is Generally Available. For more information, see xref:../hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc[Deploying {hcp} on {ibm-z-title}].
 
 [id="hcp-4-17-ibm-power-ga_{context}"]
-=== {hcp-capital} on {ibm-power-title} is Generally Available
+==== {hcp-capital} on {ibm-power-title} is Generally Available
 In this release, {hcp} on {ibm-power-title} is Generally Available. For more information, see xref:../hosted_control_planes/hcp-deploy/hcp-deploy-ibm-power.adoc[Deploying {hcp} on {ibm-power-title}].
 
 [id="bug-fixes-hcp-rn-4-17_{context}"]
-== Bug fixes
+=== Bug fixes
 
 * Previously, when a hosted cluster proxy was configured and it used an identity provider (IDP) that had an HTTP or HTTPS endpoint, the hostname of the IDP was unresolved before sending it through the proxy. Consequently, hostnames that could only be resolved by the data plane failed to resolve for IDPs. With this update, a DNS lookup is performed before sending IPD traffic through the `konnectivity` tunnel. As a result, IDPs with hostnames that can only be resolved by the data plane can be verified by the Control Plane Operator. (link:https://issues.redhat.com/browse/OCPBUGS-41371[*OCPBUGS-41371*])
 
@@ -85,7 +88,7 @@ With this release, you can configure the proxy on the Konnectivity sidecar of th
 * Previously, the bulk destroy option in the {mce} console for {VirtProductName} did not destroy a hosted cluster. With this release, this issue is resolved. (link:https://issues.redhat.com/browse/ACM-10165[*ACM-10165*])
 
 [id="known-issues-hcp-rn-4-17_{context}"]
-== Known issues
+=== Known issues
 
 * If the annotation and the `ManagedCluster` resource name do not match, the {mce} console displays the cluster as `Pending import`. The cluster cannot be used by the {mce-short}. The same issue happens when there is no annotation and the `ManagedCluster` name does not match the `Infra-ID` value of the `HostedCluster` resource.
 
@@ -131,7 +134,7 @@ To resolve these issues, configure the DNS server settings for a dual stack netw
 ** You created a hosted cluster through the command-line interface or API by specifying the hosted cluster namespace to be the same as the hosted cluster name.
 
 [id="hcp-tech-preview-features_{context}"]
-== Generally Available and Technology Preview features
+=== Generally Available and Technology Preview features
 
 Features which are Generally Available (GA) are fully supported and are suitable for production use. Technology Preview (TP) features are experimental features and are not intended for production use. For more information about TP features, see the link:https://access.redhat.com/support/offerings/techpreview[Technology Preview scope of support on the Red Hat Customer Portal].