Update VPCs user guide

(cherry picked from commit 18c8ae5)

docs/user-guide/vpcs.md

@@ -22,25 +22,25 @@ spec:
     default: # Each subnet is named, "default" subnet isn't required, but actively used by CLI
       dhcp:
         enable: true # On-demand DHCP server
-        range: # Optionally, start/end range could be specified
+        range: # Optionally, start/end range could be specified, otherwise all available IPs are used
           start: 10.10.1.10
           end: 10.10.1.99
         pxeURL: tftp://10.10.10.99/bootfilename # PXEURL (optional) to identify the PXE server to use to boot hosts; HTTP query strings are not supported
       subnet: 10.10.1.0/24 # User-defined subnet from ipv4 namespace
       gateway: 10.10.1.1 # User-defined gateway (optional, default is .1)
-      vlan: "1001" # User-defined VLAN from VLAN namespace
+      vlan: 1001 # User-defined VLAN from VLAN namespace
       isolated: true # Makes subnet isolated from other subnets within the VPC (doesn't affect VPC peering)
       restricted: true # Causes all hosts in the subnet to be isolated from each other
 
     thrird-party-dhcp: # Another subnet
       dhcp:
         relay: 10.99.0.100/24 # Use third-party DHCP server (DHCP relay configuration), access to it could be enabled using StaticExternal connection
       subnet: "10.10.2.0/24"
-      vlan: "1002"
+      vlan: 1002
 
     another-subnet: # Minimal configuration is just a name, subnet and VLAN
       subnet: 10.10.100.0/24
-      vlan: "1100"
+      vlan: 1100
 
   permit: # Defines which VPCs could communicate to each other, applied on top of subnets "isolated" flag (doesn't affect VPC peering)
     - [subnet-1, subnet-2, subnet-3] # 1, 2 and 3 subnets could communicate to each other