Update anchor link of Nodeport from #nodeport to #type-nodeport (#2348)

* Update anchor link from #nodeport to #type-nodeport in annotations.md

* Update anchor link from #nodeport to #type-nodeport in annotations.md

Author: sandipanpanda

docs/guide/ingress/annotations.md

@@ -170,7 +170,7 @@ Traffic Routing can be controlled with following annotations:
 
 - <a name="target-type">`alb.ingress.kubernetes.io/target-type`</a> specifies how to route traffic to pods. You can choose between `instance` and `ip`:
 
-    - `instance` mode will route traffic to all ec2 instances within cluster on [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport) opened for your service.
+    - `instance` mode will route traffic to all ec2 instances within cluster on [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport) opened for your service.
 
         !!!note ""
             service must be of type "NodePort" or "LoadBalancer" to use `instance` mode

docs/guide/service/annotations.md

@@ -76,7 +76,7 @@ Traffic Routing can be controlled with following annotations:
 
 - <a name="nlb-target-type">`service.beta.kubernetes.io/aws-load-balancer-nlb-target-type`</a> specifies the target type to configure for NLB. You can choose between
 `instance` and `ip`.
-    - `instance` mode will route traffic to all EC2 instances within cluster on the [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport) opened for your service.
+    - `instance` mode will route traffic to all EC2 instances within cluster on the [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport) opened for your service.
 
         !!!note ""
             service must be of type `NodePort` or `LoadBalancer` for `instance` targets