Merge pull request #107267 from v-maudel/patch-475

M47969: Fixing typo public/private

Author: PRMerger14

articles/azure-monitor/platform/diagnostics-extension-schema-windows.md

@@ -502,7 +502,7 @@ The *PublicConfig* and *PrivateConfig* are separated because in most JSON usage
 ```
 
 > [!NOTE]
-> The public config Azure Monitor sink definition has two properties, *PrincipalId* and *Secret*. These are only required for Classic VMs and Classic Cloud services. These properties should not be used for other resources.
+> The private config Azure Monitor sink definition has two properties, *PrincipalId* and *Secret*. These are only required for Classic VMs and Classic Cloud services. These properties should not be used for other resources.
 
 
 ```json
@@ -670,4 +670,4 @@ The *PublicConfig* and *PrivateConfig* are separated because in most JSON usage
 > [!NOTE]
 > The public config Azure Monitor sink definition has two properties, resourceId and region. These are only required for Classic VMs and Classic Cloud services. These properties should not be used for Resource Manager Virtual Machines or Virtual Machine Scale sets.
 > There is also an additional Private Config element for the Azure Monitor sink, that passes in a Principal Id and Secret. This is only required for Classic VMs and Classic Cloud Services. For Resource Manager VMs and VMSS the Azure Monitor definition in the private config element can be excluded.
->
+>