added etcd v2 to v3 migration guide to the related section

Signed-off-by: shivamgcodes <shivamguptaxia2@gmail.com>

Author: shivamgcodes

content/en/docs/v3.6/upgrades/upgrade_3_6.md

@@ -369,7 +369,7 @@ While upgrading, an etcd cluster supports mixed versions of etcd members, and op
 
 If this cluster has been in use since etcd v2, there are some additional requirements.
 
-First, if you are upgrading stepwise from etcd v2 to etcd v3.6, you need to take care that the database is initialized with v3 data.  See the [v2 data upgrade issue](https://github.com/etcd-io/etcd/issues/9480) for more details.
+First, if you are upgrading stepwise from etcd v2 to etcd v3.6, you need to take care that the database is initialized with v3 data.  See the [v2 data upgrade issue](https://github.com/etcd-io/etcd/issues/9480) and [etcd v2 to v3 migration guide](https://etcd.io/docs/v3.6/tutorials/how-to-migrate/) for more details.
 
 If the cluster is serving a v2 data set larger than 50MB, each newly upgraded member may take up to two minutes to catch up with the existing cluster. Check the size of a recent snapshot to estimate the total data size. In other words, it is safest to wait for 2 minutes between upgrading each member.
 
@@ -512,7 +512,7 @@ Restart the etcd server with same configuration but with the new etcd binary.
 ```diff
 -etcd-old --name ${name} \
 +etcd-new --name ${name} \
-  --data-dir /tmp/etcd/s1 \
+  --data-dir /path/to/${name}.etcd \
   --listen-client-urls http://localhost:2379 \
   --advertise-client-urls http://localhost:2379 \
   --listen-peer-urls http://localhost:2380 \