From e23493db1c8c97902a2dc6680008c438149155f6 Mon Sep 17 00:00:00 2001 From: Rowena Date: Thu, 27 Mar 2025 17:38:25 +0100 Subject: [PATCH] fix(typo): fix --- pages/vpc/how-to/create-private-network.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/vpc/how-to/create-private-network.mdx b/pages/vpc/how-to/create-private-network.mdx index 42ee45373c..1f4e0e5dca 100644 --- a/pages/vpc/how-to/create-private-network.mdx +++ b/pages/vpc/how-to/create-private-network.mdx @@ -70,7 +70,7 @@ The IPv4 CIDR block is defined at the time of creating the Private Network. You Automatically generating a CIDR block is the default (and recommended) setting when creating a Private Network. Simply follow the steps [above](#how-to-create-a-private-network) to create a Private Network, leave **Advanced Settings** at default values, and a `/22` CIDR block will be automatically generated for the Private Network. -This block is guaranteed to be unique within the VPC, and will not overlap with any of your other Private Networks. It gives 1024 private IPv4 addresses, of which 1022 are available to be allocated to resources attached to the Private Network. The first two and last two addresses in the block are not available. +This block is guaranteed to be unique within the VPC, and will not overlap with any of your other Private Networks. It gives 1024 private IPv4 addresses, of which 1020 are available to be allocated to resources attached to the Private Network. The first two and last two addresses in the block are not available. #### Defining a custom CIDR block