more updates

Author: AbhishekMallick01

articles/backup/backup-azure-diagnostic-events.md

@@ -41,36 +41,40 @@ To send your vault diagnostics data to Log Analytics:
 
 # [Recovery Services vaults](#tab/recovery-services-vaults)
 
-1. Go to your vault, and select **Diagnostic Settings**. Select **+ Add Diagnostic Setting**.
-2. Give a name to the diagnostics setting.
-3. Select the **Send to Log Analytics** check box, and select a Log Analytics workspace.
-4. Select **Resource specific** in the toggle, and select the following five events: **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupPolicy**, **AddonAzureBackupStorage**, and **AddonAzureBackupProtectedInstance**.
-5. Select **Save**.
+1. Go to your *vault*, and then select **Diagnostic Settings** > **+ Add Diagnostic Setting**.
+1. Provide a name to the *diagnostics setting*.
+1. Select the **Send to Log Analytics** checkbox, and then select a *Log Analytics workspace*.
+1. Select **Resource specific** in the toggle, and select the following five events: **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupPolicy**, **AddonAzureBackupStorage**, and **AddonAzureBackupProtectedInstance**.
+1. Select **Save**.
 
    ![Resource-specific mode](./media/backup-azure-configure-backup-reports/recovery-services-vault-diagnostics-settings.png)
 
 # [Backup vaults](#tab/backup-vaults)
 
-1. Go to your vault, and select **Diagnostic Settings**. Select **+ Add Diagnostic Setting**.
-2. Give a name to the diagnostics setting.
-3. Select the **Send to Log Analytics** check box, and select a Log Analytics workspace.
-4. Select the following events: **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupPolicy** and **AddonAzureBackupProtectedInstance**.
+1. Go to your *vault*, and then select **Diagnostic Settings** > **+ Add Diagnostic Setting**.
+2. Provide a name to the *diagnostics setting*.
+3. Select the **Send to Log Analytics** checkbox, and then select a *Log Analytics workspace*.
+4. Select the following events: **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupPolicy**, and **AddonAzureBackupProtectedInstance**.
 5. Select **Save**.
 
    ![Backup vault diagnostics settings](./media/backup-azure-configure-backup-reports/backup-vault-diagnostics-settings.png)
 
+---
+
 After data flows into the Log Analytics workspace, dedicated tables for each of these events are created in your workspace. You can query any of these tables directly. You can also perform joins or unions between these tables if necessary.
 
 > [!IMPORTANT]
-> The six events, namely, CoreAzureBackup, AddonAzureBackupJobs, AddonAzureBackupAlerts, AddonAzureBackupPolicy, AddonAzureBackupStorage, and AddonAzureBackupProtectedInstance, are supported *only* in the resource-specific mode for Recovery Services vaults in [Backup reports](./configure-reports.md). *If you try to send data for these six events in Azure diagnostics mode, no data will be visible in Backup reports.*
-> AddonAzureBackupAlerts refers to the alerts being generated by the classic alerts solution. As classic alerts solution is on deprecation path in favour of Azure Monitor based alers, we recommend you not to select this event AddonAzureBackupAlerts when configuring diagnostics settings. To send the fired Azure Monitor based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
-> For Backup vaults, since information on the frontend size and backup storage consumed is already included in the CoreAzureBackup and AddonAzureBackupProtectedInstances events (to aid query performance), the AddonAzureBackupStorage event is not applicable for Backup vault, to avoid creation of redundant tables.
+> The six events, namely, *CoreAzureBackup*, *AddonAzureBackupJobs*, *AddonAzureBackupAlerts*, *AddonAzureBackupPolicy*, *AddonAzureBackupStorage*, and *AddonAzureBackupProtectedInstance*, are supported *only* in the resource-specific mode for Recovery Services vaults in [Backup reports](configure-reports.md). *If you try to send data for these six events in Azure diagnostics mode, no data will appear in Backup reports.*
+>
+> *AddonAzureBackupAlerts* refers to the alerts being generated by the classic alerts solution. As classic alerts solution is on deprecation path in favour of Azure Monitor-based alers, we recommend you not to select the event *AddonAzureBackupAlerts* when configuring diagnostics settings. To send the fired Azure Monitor-based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
+>
+> For Backup vaults, since information on the frontend size and backup storage consumed are already included in the *CoreAzureBackup* and *AddonAzureBackupProtectedInstances* events (to aid query performance), the *AddonAzureBackupStorage event* isn't applicable for Backup vault, to avoid creation of redundant tables.
 
 ## Legacy event
 
 Traditionally, for Recovery Services vaults, all backup-related diagnostics data for a vault was contained in a single event called AzureBackupReport. The six events described here are, in essence, a decomposition of all the data contained in AzureBackupReport.
 
-Currently, we continue to support the AzureBackupReport event for Recovery Services vaults, backward compatibility in cases where users have existing custom queries on this event. Examples are custom log alerts and custom visualizations. *We recommend that you move to the [new events](#diagnostics-events-available-for-azure-backup-users) as early as possible*. The new events:
+Currently, we continue to support the *AzureBackupReport* event for Recovery Services vaults, backward compatibility in cases where you've existing custom queries on this event. For example, custom log alerts and custom visualizations. *We recommend that you move to the [new events](#diagnostics-events-available-for-azure-backup-users) as early as possible*. The new events:
 
 * Make the data much easier to work with in log queries.
 * Provide better discoverability of schemas and their structure.
@@ -79,7 +83,7 @@ Currently, we continue to support the AzureBackupReport event for Recovery Servi
 *The legacy event in Azure diagnostics mode will eventually be deprecated. Choosing the new events might help you to avoid complex migrations at a later date*. Our [reporting solution](./configure-reports.md) that uses Log Analytics will also stop supporting data from the legacy event.
 
 > [!NOTE]
-> For Backup vaults, all diagnostics events are sent to the resource-specific tables only, and hence you don't need to do any migration for Backup vaults. The below section is specific to Recovery services vaults.
+> For Backup vaults, all diagnostics events are sent to the resource-specific tables only; so, you don't need to do any migration for Backup vaults. The following section is specific to Recovery services vaults.
 
 ### Steps to move to new diagnostics settings for a Log Analytics workspace