diff --git a/docs/user/BYOnetwork.md b/docs/user/BYOnetwork.md
index a3299cc2..98edd5fe 100644
--- a/docs/user/BYOnetwork.md
+++ b/docs/user/BYOnetwork.md
@@ -8,8 +8,8 @@ You have the option to use existing network resources with SAS Viya 4 Terraform
| -: | :--- | :--- | :--- | :--- | :---|
| 0|No existing network resources | None | | Not a BYO network scenario | IaC creates the required network resources |
| 1|To work with an existing VPC | `vpc_id` | |
- VPC does not contain any Subnets or other [Network components](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Networking.html)
- VPC block size must be IPv4 with '/16' netmask (supports 65,536 IP addresses)
- `DNS hostnames` and `DNS resolution` are enabled
- [`subnets`](../CONFIG-VARS.md#networking) CIDR blocks must match with VPC IPv4 CIDR block
| Subnets, NAT Gateway and Security Groups|
-| 2|To configure all components of your VPC network - Subnets, Routes & associations and optionally Internet and NAT Gateways | `vpc_id`,
`subnet_ids.private`| `nat_id`, `subnet_ids.public`,
and
`subnet_ids.database` | - all requirements from Scenario #1
- Subnets Availability Zones must be within the [location](../CONFIG-VARS.md#required-variables)
- AWS Tags with `` value replaced with the [prefix](../CONFIG-VARS.md#required-variables) input value for
- Public Subnets:- `{"kubernetes.io/role/elb"="1"}`
- `{"kubernetes.io/cluster/-eks"="shared"}`
-Private Subnets:- `{"kubernetes.io/role/internal-elb"="1"}`
- `{"kubernetes.io/cluster/-eks"="shared"}`
See [AWS docs](https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.html) for background on subnet tag requirements to match EKS Cluster name| Security Groups |
-| 3|To configure all components of your VPC network and Security Groups and optionally Internet and NAT Gateways| `vpc_id`,
`subnet_ids.private`,
`security_group_id`,
`cluster_security_group_id`, and
`workers_security_group_id` | `nat_id`, `subnet_ids.public`,
and `subnet_ids.database` |- all requirements from Scenarios #2 and [these pre-defined Security Groups](#security-groups)
| None |
+| 2|To configure all components of your VPC network - Subnets, Routes & associations and optionally Internet and NAT Gateways | `vpc_id`,
`private` subnet list within the [subnet_ids](../CONFIG-VARS.md#use-existing) map| `nat_id`,
`public` and `database` subnet lists within the [subnet_ids](../CONFIG-VARS.md#use-existing) map | - all requirements from Scenario #1
- Subnets Availability Zones must be within the [location](../CONFIG-VARS.md#required-variables)
- AWS Tags with `` value replaced with the [prefix](../CONFIG-VARS.md#required-variables) input value for
- Public Subnets:- `{"kubernetes.io/role/elb"="1"}`
- `{"kubernetes.io/cluster/-eks"="shared"}`
-Private Subnets:- `{"kubernetes.io/role/internal-elb"="1"}`
- `{"kubernetes.io/cluster/-eks"="shared"}`
See [AWS docs](https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.html) for background on subnet tag requirements to match EKS Cluster name| Security Groups |
+| 3|To configure all components of your VPC network and Security Groups and optionally Internet and NAT Gateways| `vpc_id`,
`private` subnet list within the [subnet_ids](../CONFIG-VARS.md#use-existing) map,
`security_group_id`,
`cluster_security_group_id`, and
`workers_security_group_id` | `nat_id`,
`public` and `database` subnet lists within the [subnet_ids](../CONFIG-VARS.md#use-existing) map |- all requirements from Scenarios #2 and [these pre-defined Security Groups](#security-groups)
| None |
**Note**: The `byo_network_scenario` IAC output value is informational only and is intended to convey the BYO network scenario that IAC has selected according to the [Use Existing](../CONFIG-VARS.md#use-existing) input variable values provided to IAC.