Fix typo in cache-how-to-premium-persistence.md

batkaevruslan · web-flow · commit e3bf32dcba36 · 2025-03-18T15:43:57.000+05:00
diff --git a/articles/azure-cache-for-redis/cache-how-to-premium-persistence.md b/articles/azure-cache-for-redis/cache-how-to-premium-persistence.md
@@ -12,7 +12,7 @@ ms.date: 02/21/2025
 
 > [!IMPORTANT]
 >
-> The data persistence functionality provides resilience for unexpected Redis node failures. Data persistence isn't a data backup or point in time recovery (PITR) feature. If corrupted data is written to the Redis instance, th corrupted data is also persisted. To make backups of your Redis instance, use the [export feature](cache-how-to-import-export-data.md).  
+> The data persistence functionality provides resilience for unexpected Redis node failures. Data persistence isn't a data backup or point in time recovery (PITR) feature. If corrupted data is written to the Redis instance, the corrupted data is also persisted. To make backups of your Redis instance, use the [export feature](cache-how-to-import-export-data.md).  
 >
 
 > [!WARNING]

Original file line number	Diff line number	Diff line change
`@@ -12,7 +12,7 @@ ms.date: 02/21/2025`
`12`	`12`
`13`	`13`	`> [!IMPORTANT]`
`14`	`14`	`>`
`15`		`-> The data persistence functionality provides resilience for unexpected Redis node failures. Data persistence isn't a data backup or point in time recovery (PITR) feature. If corrupted data is written to the Redis instance, th corrupted data is also persisted. To make backups of your Redis instance, use the [export feature](cache-how-to-import-export-data.md).`
	`15`	`+> The data persistence functionality provides resilience for unexpected Redis node failures. Data persistence isn't a data backup or point in time recovery (PITR) feature. If corrupted data is written to the Redis instance, the corrupted data is also persisted. To make backups of your Redis instance, use the [export feature](cache-how-to-import-export-data.md).`
`16`	`16`	`>`
`17`	`17`
`18`	`18`	`> [!WARNING]`