addressed peer-review inputs

Author: AbhishekMallick-MS

articles/backup/automation-backup.md

@@ -2,7 +2,7 @@
 title: Automation in Azure Backup
 description: Provides a summary of automation capabilities offered by Azure Backup.
 ms.topic: conceptual
-ms.date: 09/15/2022
+ms.date: 03/21/2024
 ms.service: backup
 ms.custom: engagement-fy23
 author: AbhishekMallick-MS
@@ -61,7 +61,7 @@ See the [sample ARG queries](query-backups-using-azure-resource-graph.md#sample-
 
 ### Automate responses/actions
 
-The automation of responses for transient Backup job failures helps you ensure that you've the right number of reliable backups to restore from. This also helps to avoid unintentional breaches in your [RPO](azure-backup-glossary.md#rpo-recovery-point-objective).
+The automation of responses for transient Backup job failures helps you ensure that you've the right number of reliable backups to restore from. This also helps to avoid unintentional breaches in your [RPO](azure-backup-glossary.md#recovery-point-objective-rpo).
 
 You can set up a workflow to retry Backup jobs using a combination of Azure Automation Runbooks, PowerShell, and ARG. This helps in scenarios where Backup jobs have failed due to transient error or planned/unplanned outage.
 

articles/backup/azure-backup-glossary.md

@@ -259,15 +259,15 @@ A user-defined rule that specifies how long backups should be retained.
 
 ## Recovery Point Objective (RPO)
 
-PO indicates the maximum acceptable amount of data-loss measured in time. For example, if a disaster occurs at *12:00 PM* and the last backup was at *10:00 AM*, the RPO is *two hours*. This means that the organization is willing to accept losing two hours’ worth of data.
+RPO indicates the maximum acceptable amount of data loss measured in time. For example, if a disaster occurs at *12:00 PM* and the last backup was at *10:00 AM*, the RPO is *two hours*. This means that the organization is willing to accept losing two hours’ worth of data.
 
 ## Recovery Time Objective (RTO)
 
-RTO is the target time within which a business process must be restored after a disaster occurs to avoid unacceptable consequences. For instance, if a critical application goes down due to a server failure, and the business can only tolerate a *maximum of four hours of downtime*, then the RTO is *four hours*.
+RTO is the target time within which a business process must be restored after a disaster occurs to avoid unacceptable consequences. For instance, if a critical application goes down due to a server failure and the business can only tolerate a *maximum of four hours of downtime*, then the RTO is *four hours*.
 
-The following example scenario describes both RPO and RTO concepts:
+The following example scenario describes both the RPO and RTO concepts:
 
-Your company has an RPO of *1 hour* for your customer database, which means you perform backups every hour. If a data loss incident occurs, you'll lose not more than *one hour of data*. When you set RTO to *3 hours*, then in the event of a system failure, you aim to restore access to the database within 3 hours to minimize impact on operations.
+Your organization has an RPO of *one hour* for your customer database, which means you perform backups every hour. If a data loss incident occurs, you'll lose not more than *one hour of data*. When you set RTO to *three hours*, then in the event of a system failure, you aim to restore access to the database within three hours to minimize the impact on operations.
 
 ## Scheduled backup
 

articles/backup/backup-azure-arm-restore-vms.md

@@ -3,7 +3,7 @@ title: Restore VMs by using the Azure portal
 description: Restore an Azure virtual machine from a recovery point by using the Azure portal, including the Cross Region Restore feature.
 ms.reviewer: nikhilsarode
 ms.topic: how-to
-ms.date: 01/22/2024
+ms.date: 03/21/2024
 ms.service: backup
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
@@ -220,7 +220,7 @@ If CRR is enabled, you can view the backup items in the secondary region.
 
 The secondary region restore user experience will be similar to the primary region restore user experience. When configuring details in the Restore Configuration pane to configure your restore, you'll be prompted to provide only secondary region parameters.
 
-Currently, secondary region [RPO](azure-backup-glossary.md#rpo-recovery-point-objective) is _36 hours_. This is because the RPO in the primary region is _24 hours_ and can take up to _12 hours_ to replicate the backup data from the primary to the secondary region.
+Currently, secondary region [RPO](azure-backup-glossary.md#recovery-point-objective-rpo) is _36 hours_. This is because the RPO in the primary region is _24 hours_ and can take up to _12 hours_ to replicate the backup data from the primary to the secondary region.
 
 ![Choose VM to restore](./media/backup-azure-arm-restore-vms/sec-restore.png)