Skip to content

Commit b9d09a3

Browse files
authored
fixing Acrolinx Words/Phrases
1 parent 11e4d80 commit b9d09a3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/backup/protect-backups-from-ransomware-faq.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ sections:
8181
- [Monitor your backups with Backup Explorer](monitor-azure-backup-with-backup-explorer.md).
8282
- [Monitor backup workloads using Azure portal (using Recovery Services vault)](backup-azure-monitoring-built-in-monitor.md).
8383
- [Monitor backup health using Azure monitor metrics](backup-azure-monitoring-built-in-monitor.md).
84-
- [Custom monitoring and alerting using azure monitor Log Analytics workspace](backup-azure-monitoring-use-azuremonitor.md).
84+
- [Custom monitoring and alerting using Azure monitor Log Analytics workspace](backup-azure-monitoring-use-azuremonitor.md).
8585

8686
- **Validate backups periodically by performing test restores**.
8787

@@ -121,5 +121,5 @@ sections:
121121
answer: No, the infected recovery point (that is, backed-up data containing infected data) can’t spread to previous non-infected recovery points.
122122

123123
- question: How can I extend the expiration of recovery points in case of impact?
124-
answer: If you need more time to investigate and recover in case of an impact, you can extend expiration to ensure the recovery points aren't cleaned up (as per policy). [Learn more](backup-architecture.md#additional-reference), so that they aren’t deleted by the retention policy
124+
answer: If you need more time to investigate and recover in case of an impact, you can extend expiration to ensure the recovery points aren't cleaned up (as per policy). [Learn more](backup-architecture.md#additional-reference), so that they aren’t deleted by the retention policy.
125125

0 commit comments

Comments
 (0)