Update hdinsight-aks-release-notes.md

Author: yeturis

articles/hdinsight-aks/release-notes/hdinsight-aks-release-notes.md

@@ -38,9 +38,11 @@ You can refer to [What's new](../whats-new.md) page for all the details of the f
 ### New Features
 
 **Apache Flink Application Mode Cluster**
+
  Application mode clusters are designed to support dedicated resources for large and long-running jobs. When you have resource-intensive or extensive data processing tasks, you can use the [Application Mode Cluster](https://flink.apache.org/2020/07/14/application-deployment-in-flink-current-state-and-the-new-application-mode/#application-mode). This mode allows you to allocate dedicated resources for specific Apache Flink applications, ensuring that they have the necessary computing power and memory to handle large workloads effectively.  
 
 **Private Clusters for HDInsight on AKS**
+
 With private clusters, and outbound cluster settings you can now control ingress and egress traffic from HDInsight on AKS cluster pools and clusters.
 
 1. Use Azure Firewall or Network Security Groups (NSGs) to control the egress traffic, when you opt to use outbound cluster pool with load balancer.
@@ -49,14 +51,15 @@ With private clusters, and outbound cluster settings you can now control ingress
 1. Avoid creating public IPs for the cluster. Use private ingress feature on your clusters.
 
 **In place Upgrade**
+
 Upgrade your clusters and cluster pools with the latest software updates. This means that you can enjoy the latest cluster package hotfixes, security updates, and AKS patches, without recreating clusters.  
 
 
 ### Known issues
 
 - **Workload identity limitation:**
-  - there's a known [limitation](/azure/aks/workload-identity-overview#limitations) when transitioning to workload identity. This limitation is due to the permission-sensitive nature of FIC operations. Users can't perform deletion of a cluster by deleting the resource group. Cluster deletion requests must be triggered by the application/user/principal with FIC/delete permissions. In case, the FIC deletion fails, the high-level cluster deletion also fails.
-  - **User Assigned Managed Identities (UAMI)** support is limited – there's a limit of 20 FICs per UAMI. You can only create 20 Federated Credentials on an identity. In HDInsight on AKS cluster, FIC (Federated Identity Credential) and SA are one-to-one mapping and only 20SAs can be created against an MSI. If you want to create more clusters, then provide different MSIs to overcome the limitation.
+  - There's a known [limitation](/azure/aks/workload-identity-overview#limitations) when transitioning to workload identity. This limitation is due to the permission-sensitive nature of FIC operations. Users can't perform deletion of a cluster by deleting the resource group. Cluster deletion requests must be triggered by the application/user/principal with FIC/delete permissions. In case, the FIC deletion fails, the high-level cluster deletion also fails.
+  - **User Assigned Managed Identities (UAMI)** support – There's a limit of 20 FICs per UAMI. You can only create 20 Federated Credentials on an identity. In HDInsight on AKS cluster, FIC (Federated Identity Credential) and SA have one-to-one mapping and only 20 SAs can be created against an MSI. If you want to create more clusters, then you are required to provide different MSIs to overcome the limitation.
 
 
 ### Operating System version