Skip to content

Commit 3530b6f

Browse files
committed
Fix typo
PostGreSQL -> PostgreSQL
1 parent 7410cb3 commit 3530b6f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/backup/backup-postgresql-cli.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ After the vault is created, let's create a Backup policy to protect Azure Postgr
5656

5757
## Create a Backup policy
5858

59-
### Understanding PostGreSQL backup policy
59+
### Understanding PostgreSQL backup policy
6060

6161
While disk backup offers multiple backups per day and blob backup is a _continuous_ backup with no trigger, PostgreSQL backup offers Archive protection. The backup data that's first sent to the vault can be then moved to the _archive_ tier as per a defined rule or a _lifecycle_. In this context, let's understand the backup policy object for PostgreSQL.
6262

@@ -268,7 +268,7 @@ Once the vault and policy are created, there are three critical points that you
268268

269269
### Key entities involved
270270

271-
#### PostGreSQL database to be protected
271+
#### PostgreSQL database to be protected
272272

273273
Fetch the Azure Resource Manager ID (ARM ID) of PostgreSQL to be protected. This serves as the identifier of the database. We'll use an example of a database named **empdb11** under a PostgreSQL server **testposgresql**, which is present in the resource group **ossrg** under a different subscription.
274274

0 commit comments

Comments
 (0)