table formatting

Author: AbbyMSFT

articles/azure-monitor/alerts/alerts-processing-rules.md

@@ -64,22 +64,13 @@ Alert rule ID |  The rule applies only to alerts from a specific alert rule. The
 Alert rule name |  The rule applies only to alerts with this alert rule name. It can also be useful with a **Contains** operator. |
 Description |  The rule applies only to alerts that contain the specified string within the alert rule description field. |
 Monitor condition |  The rule applies only to alerts with the specified monitor condition, either **Fired** or **Resolved**. |
-Monitor service |  The rule applies only to alerts from any of the specified monitoring services that are sending the signal. Different services are available depending on the type of signal. For example: <br>
-**Platform**: For metric signals, the monitor service is the metric namespace. ‘Platform’ means the metrics are provided by the resource provider, namely 'Azure'.<br>**Azure.ApplicationInsights**: Customer-reported metrics, sent by the Application Insights SDK.<br>
-**Azure.VM.Windows.GuestMetrics**: VM guest metrics, collected by an extension running on the VM. Can include built-in operating system perf counters, and custom perf counters.<br>
-**/<Custom namespaces/>**: A custom metric namespace, containing custom metrics sent with the Azure Monitor Metrics API.<br>
-**Log Analytics**: The service that provides the ‘Custom log search’ and ‘Log (saved query)’ signals.<br>
-**Activity Log – Administrative**: The service that provides the ‘Administrative’ activity log events.<br>
-**Activity Log – Policy**: The service that provides the 'Policy' activity log events.<br>
-**Activity Log – Autoscale** The service that provides the ‘Autoscale’ activity log events.<br>
-**Activity Log – Security**: The service that provides the ‘Security’ activity log events.<br>
-**Resource health**: The service that provides the resource-level health status.<br>
-**Service health**: The service that provides the subscription-level health status.|
+Monitor service |  The rule applies only to alerts from any of the specified monitoring services that are sending the signal. Different services are available depending on the type of signal. For example: |
 Resource |  The rule applies only to alerts from the specified Azure resource. For example, you can use this filter with **Does not equal** to exclude one or more resources when the rule's scope is a subscription. | 
 Resource group |  The rule applies only to alerts from the specified resource groups. For example, you can use this filter with **Does not equal** to exclude one or more resource groups when the rule's scope is a subscription. | 
 Resource type |  The rule applies only to alerts on resources from the specified resource types, such as virtual machines. You can use **Equals** to match one or more specific resources. You can also use **Contains** to match a resource type and all its child resources. For example, use `resource type contains "MICROSOFT.SQL/SERVERS"` to match both SQL servers and all their child resources, like databases.
 Severity |  The rule applies only to alerts with the selected severities. |
 
+
 #### Alert processing rule filters
 
 * If you define multiple filters in a rule, all the rules apply. There's a logical AND between all filters.