Update 2.13.0.md

Author: rasika-chivate

docs/release-notes/2.13.0.md

@@ -4,7 +4,7 @@
 [Installation](../installation.md){.md-button}
 
 
-Percona Backup for MongoDB (PBM) is a distributed, low-impact solution for creating consistent backups of MongoDB sharded clusters and replica sets, and for restoring those backups to a specific point in time.
+Percona Backup for MongoDB (PBM) is a distributed, low-impact solution for creating consistent backups of MongoDB sharded clusters and replica sets, and restoring them to a specific point in time.
 
 ## Release Highlights
 
@@ -56,19 +56,19 @@ Percona Backup for MongoDB (PBM) is a distributed, low-impact solution for creat
 
 - [PBM-1663](https://perconadev.atlassian.net/browse/PBM-1663): Enhanced the `pbm status` and `pbm list` commands to display the **Profile (storage)** associated with each backup, making it easier to identify where backups are located. A new option has also been added to filter results by a specific Profile, showing only backups for the chosen storage. 
 
-- [PBM-1665](https://perconadev.atlassian.net/browse/PBM-1665): Point-in-time recovery (PITR) now continues uninterrupted  when logical backups are performed using external storage profiles. The backup process on external storage no longer interrupts oplog slicing on the main storage. PBM saves oplog chunks related to such backups on both the main and external storages, ensuring consistent PITR coverage.
+- [PBM-1665](https://perconadev.atlassian.net/browse/PBM-1665): Point-in-time recovery (PITR) now continues uninterrupted  when logical backups are performed using external storage profiles. The backup process on external storage no longer interrupts oplog slicing on the main storage. PBM saves oplog chunks for such backups on both the main and external storage, ensuring consistent PITR coverage.
 
 - [PBM-1673](https://perconadev.atlassian.net/browse/PBM-1673): Improved restore output by clarifying oplog replay messages, making progress and restore state easier to interpret.
 
-- [PBM-1690](https://perconadev.atlassian.net/browse/PBM-1690): Percona Backup for MongoDB now supports restarting `pbm-agent` **only at the copyReady** step during external (snapshot-based) restores. At this stage, `mongod` is stopped and the data directory has been cleared, so nodes remain on hold awaiting new snapshot data files to be provided via an external mechanism (for example, snapshot restore or rsync).
+- [PBM-1690](https://perconadev.atlassian.net/browse/PBM-1690): Percona Backup for MongoDB now supports restarting `pbm-agent` **only at the copyReady** step during external (snapshot-based) restores. At this stage, `mongod` is stopped, and the data directory has been cleared, so nodes remain on hold, awaiting new snapshot data files provided via an external mechanism (for example, snapshot restore or rsync).
 
 ## Fixed bugs
 
 - [PBM-1488](https://perconadev.atlassian.net/browse/PBM-1488): Fixed an issue where Point-in-Time Recovery (PITR) would stop saving oplog slices if a failure occurred during the oplog copy process from a backup.
 
-- [PBM-1561](https://perconadev.atlassian.net/browse/PBM-1561): Selective logical restores in sharded clusters now work correctly when the target database or collection already exists. PBM no longer fails due to pre-existing namespaces; during cleanup it drops only the namespaces specified with `--ns` using `_shardsvrDropCollection` for `--ns "db.coll"` and `_shardsvrDropDatabase` for `--ns "db.*".` The same fix applies to PITR restores (`--time`).
+- [PBM-1561](https://perconadev.atlassian.net/browse/PBM-1561): Selective logical restores in sharded clusters now work correctly when the target database or collection already exists. PBM no longer fails due to pre-existing namespaces. During cleanup, it drops only the namespaces specified with `--ns` using `_shardsvrDropCollection` for `--ns "db.coll"` and `_shardsvrDropDatabase` for `--ns "db.*".` The same fix applies to PITR restores (`--time`).
 
-- [PBM-1614](https://perconadev.atlassian.net/browse/PBM-1614): Resolved issues with backup metadata serialization and error handling. PBM now reliably encodes/decodes and persists metadata in external storage by using a value type (avoiding nil pointer cases), provides more descriptive errors across backup workflows, and includes new MinIO-based tests to validate metadata serialization round-trips.
+- [PBM-1614](https://perconadev.atlassian.net/browse/PBM-1614): Resolved issues with backup metadata serialization and error handling. PBM now reliably encodes/decodes and persists metadata in external storage using a value type (avoiding nil-pointer cases), provides more descriptive errors across backup workflows, and includes new MinIO-based tests to validate metadata serialization round-trips.
 
 - [PBM-1691](https://perconadev.atlassian.net/browse/PBM-1691): Resolved an issue where the PBM CLI exposed SSE credentials in JSON output.