Update private-clusters.md

mosbahmajed · web-flow · commit 1377068d4c78 · 2023-08-02T18:44:16.000+03:00
fixing minor change
diff --git a/articles/aks/private-clusters.md b/articles/aks/private-clusters.md
@@ -111,7 +111,7 @@ You can configure private DNS zones using the following parameters:
   * If you are specifying a `<subzone>` there is a 32 character limit for the `<subzone>` name.
 
 >[!NOTE]
->**CUSTOM_PRIVATE_DNS_ZONE_RESOURCE_ID can be configured using an ARM Template in addition to the Azure CLI. `privateDNSZone` accepts the private DNZ zone resourceID as shown in the following example:
+>**CUSTOM_PRIVATE_DNS_ZONE_RESOURCE_ID** can be configured using an ARM Template in addition to the Azure CLI. `privateDNSZone` accepts the private DNZ zone resourceID as shown in the following example:
 >
 >```json
 >properties.apiServerAccessProfile.privateDNSZone.

Original file line number	Diff line number	Diff line change
`@@ -111,7 +111,7 @@ You can configure private DNS zones using the following parameters:`
`111`	`111`	* If you are specifying a `<subzone>` there is a 32 character limit for the `<subzone>` name.
`112`	`112`
`113`	`113`	`>[!NOTE]`
`114`		->**CUSTOM_PRIVATE_DNS_ZONE_RESOURCE_ID can be configured using an ARM Template in addition to the Azure CLI. `privateDNSZone` accepts the private DNZ zone resourceID as shown in the following example:
	`114`	+>CUSTOM_PRIVATE_DNS_ZONE_RESOURCE_ID can be configured using an ARM Template in addition to the Azure CLI. `privateDNSZone` accepts the private DNZ zone resourceID as shown in the following example:
`115`	`115`	`>`
`116`	`116`	>```json
`117`	`117`	`>properties.apiServerAccessProfile.privateDNSZone.`