Update minor typo in VPC and Subnet Considerations page (#560)

This commit fixes a typo in Karpenter link

content/networking/subnets/index.md

@@ -134,7 +134,7 @@ AWS Regions provide multiple physically separated and isolated Availability Zone
 
 Kubelet running on nodes automatically adds labels to the node object such as [`topology.kubernetes.io/region=us-west-2`, and `topology.kubernetes.io/zone=us-west-2d`](http://topology.kubernetes.io/region=us-west-2,topology.kubernetes.io/zone=us-west-2d). We recommend to use node labels in conjunction with [Pod topology spread constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) to control how Pods are spread across zones. These hints enable Kubernetes [scheduler](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/) to place Pods for better expected availability, reducing the risk that a correlated failure affects your whole workload. Please refer [Assigning nodes to Pods](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector) to see examples for node selector and AZ spread constraints.
 
-You can define the subnets or availability zones when you create nodes. The nodes are placed in cluster subnets if no subnets are configured. EKS support for managed node groups automatically spreads the nodes across multiple availability zones on available capacity. [Karpenter](https://karpenter.sh/)will honor the AZ spread placement by scaling nodes to specified AZs if workloads define topology spread limits.
+You can define the subnets or availability zones when you create nodes. The nodes are placed in cluster subnets if no subnets are configured. EKS support for managed node groups automatically spreads the nodes across multiple availability zones on available capacity. [Karpenter](https://karpenter.sh/) will honor the AZ spread placement by scaling nodes to specified AZs if workloads define topology spread limits.
 
 AWS Elastic Load Balancers are managed by the AWS Load Balancer Controller for a Kubernetes cluster. It provisions an Application Load Balancer (ALB) for Kubernetes ingress resources and a Network Load Balancer (NLB) for Kubernetes services of type Loadbalancer. The Elastic Load Balancer controller uses [tags](https://aws.amazon.com/premiumsupport/knowledge-center/eks-vpc-subnet-discovery/) to discover the subnets. ELB controller requires a minimum of two availability zones (AZs) to provision ingress resource successfully. Consider setting subnets in at least two AZs to take advantage of geographic redundancy's safety and reliability.