@@ -22,7 +22,7 @@ object storage system. It allows you to configure:
2222 server-side encryption—under ` .spec.configuration.wal `
2323- ** Base backup options** —with similar settings for compression, concurrency,
2424 and encryption—under ` .spec.configuration.data `
25- - ** Retention policies** to manage the lifecycle of archived WALs and backups
25+ - ** Retention policies** to manage the life-cycle of archived WALs and backups
2626 via ` .spec.configuration.retentionPolicy `
2727
2828::: tip
@@ -34,14 +34,15 @@ WAL files are archived in the `wals` directory, while base backups are stored
3434as ** tarballs** in the ` base ` directory, following the
3535[ Barman Cloud convention] ( https://docs.pgbarman.org/cloud/latest/usage/#object-store-layout ) .
3636
37- The plugin integrates seamlessly with CloudNativePG’s ` Backup ` and
37+ The plugin integrates seamlessly with CloudNativePG and its ` Backup ` and
3838` ScheduledBackup ` resources, supporting backups from both primary and
3939[ standby instances] ( https://cloudnative-pg.io/documentation/current/backup/#backup-from-a-standby )
40- —including designated primaries in [ replica cluster topologies] ( https://cloudnative-pg.io/documentation/current/replica_cluster/ ) .
40+ —including designated primaries in a distributed topology with
41+ [ replica clusters] ( https://cloudnative-pg.io/documentation/current/replica_cluster/ ) .
4142
4243## About Barman Cloud
4344
44- Instead of relying on a traditional, centralised Barman server, the plugin
45+ Instead of relying on a traditional, centralized Barman server, the plugin
4546orchestrates backup operations directly within the Kubernetes cluster using the
4647following tools from the [ ` barman-cloud ` ] ( https://pgbarman.org ) suite:
4748
@@ -122,7 +123,7 @@ For a deeper comparison, see the [Barman GitHub benchmark discussion](https://gi
122123
123124# # Backup Object Tagging
124125
125- You can tag backup artefacts (base backups, WAL files, history files) using
126+ You can tag backup artifacts (base backups, WAL files, history files) using
126127key-value metadata through the following fields in `.spec.configuration` :
127128
128129- `tags` : tags for base backups and WALs
0 commit comments