pr feedback

Author: bragi92

articles/azure-monitor/essentials/prometheus-metrics-enable.md

@@ -332,12 +332,26 @@ Deploy the template with the parameter file using any valid method for deploying
 
 As of version `6.4.0-main-02-22-2023-3ee44b9e` windows metric collection has been enabled for the AKS clusters. Onboarding to the Azure Monitor Metrics Addon will enable the windows daemonset pods to start running on your nodepools(Windows Server 2019 and Windows Server 2022 are both supported). Please follow the below mentioned steps so that the pods are able to collect metrics from your windows nodepools.
 
-- For accessing windows metrics you must manually install the windows exporter on AKS nodes. Please enable the following collectors : `[defaults],container,memory,process,cpu_info`. You can deploy the following [YAML](https://github.com/prometheus-community/windows_exporter/blob/master/kubernetes/windows-exporter-daemonset.yaml) file using `kubectl apply -f windows-exporter-daemonset.yaml`
-- Please refer to the [customize configuration section](./prometheus-metrics-scrape-configuration.md#metrics-addon-settings-configmap) and enable the `windowsexporter` and `windowsexporter` boolean to true by applying the ama-metrics-settings-configmap on your cluster
-- Please use the CLI option `--enable-windows-recording-rules` while onboarding to enable the recording rules required for the default dashboards
-- If using ARM/Bicep/Policy to onboard please enable the windows recording rules by settings `enableWindowsRecordingRules` to true in the parameters file.
-- If the cluster is already onbaorded to Azure Monitor Metrics and you want to enable windows recording rule groups. Please use the following [ARM Tempalte](https://github.com/Azure/prometheus-collector/blob/kaveesh/windows_recording_rules/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRules.json) and [Parameters](https://github.com/Azure/prometheus-collector/blob/kaveesh/windows_recording_rules/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRulesParameters.json) file to create the rule groups.
+1. Manually install the windows exporter on AKS nodes to access windows metrics.
+   Enable the following collectors :
 
+   * `[defaults]`
+   * `container`
+   * `memory`
+   * `process`
+   * `cpu_info`
+
+   Deploy the [windows-exporter-daemonset YAML](https://github.com/prometheus-community/windows_exporter/blob/master/kubernetes/windows-exporter-daemonset.yaml) file
+   ```
+       kubectl apply -f windows-exporter-daemonset.yaml
+   ```
+2. Apply the [ama-metrics-settings-configmap](https://github.com/Azure/prometheus-collector/blob/main/otelcollector/configmaps/ama-metrics-settings-configmap.yaml) to your cluster, setting the `windowsexporter` and `windowskubeproxy` booleans to rue`. For more information see [Metrics addon settings configmap](./prometheus-metrics-scrape-configuration.md#metrics-addon-settings-configmap).
+3. While onboarding, enable the recording rules required for the default dashboards.
+
+   * For CLI include the option `--enable-windows-recording-rules`.
+   * For ARM, Bicep, or Policy, set `enableWindowsRecordingRules` to `true` in the parameters file.
+
+   If the cluster is already onbaorded to Azure Monitor Metrics, to enable windows recording rule groups use this [ARM Tempalte](https://github.com/Azure/prometheus-collector/blob/kaveesh/windows_recording_rules/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRules.json) and [Parameters](https://github.com/Azure/prometheus-collector/blob/kaveesh/windows_recording_rules/AddonArmTemplate/WindowsRecordingRuleGroupTemplate/WindowsRecordingRulesParameters.json) file to create the rule groups.
 
 ## Verify Deployment
 
@@ -394,13 +408,16 @@ ama-metrics-ksm-5fcf8dffcd      1         1         1       11h
 ## Uninstall metrics addon
 Currently, Azure CLI is the only option to remove the metrics addon and stop sending Prometheus metrics to Azure Monitor managed service for Prometheus.
 
-If you don't already have it, install the aks-preview extension with the following command.
+Install the `aks-preview` extension using the following command:
+
+```
+az extension add --name aks-preview
+```
 
-The `aks-preview` extension needs to be installed using the following command. For more information on how to install a CLI extension, see [Use and manage extensions with the Azure CLI](/cli/azure/azure-cli-extensions-overview).
+For more information on installing a CLI extension, see [Use and manage extensions with the Azure CLI](/cli/azure/azure-cli-extensions-overview).
 
 > [!NOTE]
-> Please upgrade your az cli version to the latest version and ensure that the aks-preview version you're using is greater than or equal to '0.5.132'. You can find out the version using the `az version` command.
-
+> Upgrade your az cli version to the latest version and ensure that the aks-preview version you're using is at least '0.5.132'. Find your current version using the `az version`.
 ```azurecli
 az extension add --name aks-preview
 ```

articles/azure-monitor/essentials/prometheus-metrics-scrape-default.md

@@ -137,8 +137,10 @@ The following metrics are collected by default from each default target. All oth
 
 ## Targets scraped for windows
 
+There are two default jobs that can be run for windows which scrape metrics required for the dashboards specific to windows.
+
 > [!NOTE]
-> This requires an update in the ama-metrics-settings-configmap and installing windows exporter on all windows nodepools. Please refer to the enablement document for more information.
+> This requires an update in the ama-metrics-settings-configmap and installing windows exporter on all windows nodepools. Please refer to the [enablement document](./prometheus-metrics-enable.md#enable-prometheus-metric-collection) for more information
 
 - `windows-exporter` (`job=windows-exporter`)
 - `kube-proxy-windows` (`job=kube-proxy-windows`)