Fixed some reported issues

Author: AbbyMSFT

.openpublishing.redirection.azure-monitor.json

@@ -102,7 +102,7 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/alerts/alerts-metric-overview.md" ,
-            "redirect_url": "/azure/azure-monitor/alerts/alert-types.md#metric-alerts",
+            "redirect_url": "/azure/azure-monitor/alerts/alert-types.md",
             "redirect_document_id": false
         },
         {
@@ -112,12 +112,12 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/alerts/alerts-unified-log.md" ,
-            "redirect_url": "/azure/azure-monitor/alerts/alert-types.md#log-alerts",
+            "redirect_url": "/azure/azure-monitor/alerts/alert-types.md",
             "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/azure-monitor/alerts/activity-log-alerts.md" ,
-            "redirect_url": "/azure/azure-monitor/alerts/alert-types.md#activity-log-alerts",
+            "redirect_url": "/azure/azure-monitor/alerts/alert-types.md",
             "redirect_document_id": false
         },
         {

articles/azure-monitor/alerts/alerts-log.md

@@ -118,10 +118,11 @@ You can also [create log alert rules using Azure Resource Manager templates](../
 > [!NOTE]
 > This section above describes creating alert rules using the new alert rule wizard. 
 > The new alert rule experience is a little different than the old experience. Please note these changes:
-> - Previously, search results were included in the payloads of the triggered alert and its associated notifications. This was a limited and error prone solution. To get detailed context information about the alert so that you can decide on the appropriate action :
->   - The recommended best practice it to use [Dimensions](alerts-unified-log.md#split-by-alert-dimensions). Dimensions provide the column value that fired the alert, giving you context for why the alert fired and how to fix the issue.
->    - When you need to investigate in the logs, use the link in the alert to the search results in Logs.
->    - If you need the raw search results or for any other advanced customizations, use Logic Apps.
+> - Previously, search results were included in the payloads of the triggered alert and its associated notifications. This was a limited solution, since the email included only 10 rows from the unfiltered results while the webhook payload contained 1000 unfiltered results.
+>    To get detailed context information about the alert so that you can decide on the appropriate action :
+>     - We recommend using [Dimensions](alerts-unified-log.md#split-by-alert-dimensions). Dimensions provide the column value that fired the alert, giving you context for why the alert fired and how to fix the issue.
+>     - When you need to investigate in the logs, use the link in the alert to the search results in Logs.
+>     - If you need the raw search results or for any other advanced customizations, use Logic Apps.
 > - The new alert rule wizard does not support customization of the JSON payload.
 >   - Use custom properties in the [new API](/rest/api/monitor/scheduledqueryrule-2021-08-01/scheduled-query-rules/create-or-update#actions) to add static parameters and associated values to the webhook actions triggered by the alert.
 >    - For more advanced customizations, use Logic Apps.