Update migration doc (#2361)

* Update migration doc

* Avoid export steps

* dummy commit for ci trigger

Author: phanimarupaka

site/installation/migration.md

@@ -212,15 +212,13 @@ $ DEMO_HOME=$(mktemp -d); cd $DEMO_HOME
 ```
 
 ```shell
-$ export ORG_NAME=example-org; export PKG_DIR=example
+# replace it with your package repo uri
+$ git clone https://github.com/GoogleContainerTools/kpt-functions-catalog.git
 ```
 
 ```shell
-$ export PKG_REPO=https://github.com/${ORG_NAME}/${PKG_DIR}.git
-```
-
-```shell
-$ git clone $PKG_REPO
+# cd to the package directory which you want to migrate
+$ cd kpt-functions-catalog/testdata/fix/nginx-v1alpha1
 ```
 
 ```shell
@@ -233,7 +231,12 @@ Invoke `gcr.io/kpt-fn/fix` function on the kpt package.
 
 ```shell
 # you must be using 1.0+ version of kpt
-$ kpt fn eval ${PKG_DIR} --image gcr.io/kpt-fn/fix:v0.2 --include-meta-resources --truncate-output=false
+$ kpt fn eval --image gcr.io/kpt-fn/fix:v0.2 --include-meta-resources --truncate-output=false
+```
+
+```shell
+# observe the changes done by the fix function
+$ git diff
 ```
 
 ##### Changes made by the function
@@ -282,8 +285,8 @@ Test your migrated kpt package end-to-end and make sure that the
 functionality is as expected. `gcr.io/kpt-fn/fix` is a helper for migration and
 doesn't guarantee functional parity.
 
-Finally, publish your package to git by upgrading the major version so that your
-consumers can fetch with the specific version.
+Finally, [publish your package] to git by upgrading the version so that your
+consumers can fetch the specific version of the package.
 
 ### For Package Consumers
 
@@ -300,22 +303,15 @@ and migrate the local customizations(if any) already performed to their existing
 $ DEMO_HOME=$(mktemp -d); cd $DEMO_HOME
 ```
 
-```shell
-$ export ORG_NAME=example-org; export PKG_DIR=example
-```
-
-```shell
-$ export PKG_REPO=https://github.com/${ORG_NAME}/${PKG_DIR}.git
-```
-
 ```shell
 # verify the version of kpt
 $ kpt version
 1.0.0+
 ```
 
 ```shell
-$ kpt pkg get $PKG_REPO
+# fetch the package with upgraded version
+$ kpt pkg get https://github.com/GoogleContainerTools/kpt-functions-catalog.git/testdata/fix/nginx-v1@master
 ```
 
 - You might have performed some customizations to your existing package such as,
@@ -326,7 +322,7 @@ $ kpt pkg get $PKG_REPO
 - Render the package resources with customizations
 
 ```shell
-$ kpt fn render $PKG_DIR
+$ kpt fn render nginx-v1/
 ```
 
 - The step is only applicable if you're using `kpt live` functionality.
@@ -383,3 +379,4 @@ kpt `v0.39`) to `v1` version(compatible with kpt `v1.0`).
 [kpt-functions-catalog]: https://catalog.kpt.dev/
 [v1alpha1 kptfile]: https://github.com/GoogleContainerTools/kpt/blob/master/pkg/kptfile/pkgfile.go#L39
 [git clone]: https://git-scm.com/docs/git-clone
+[publish your package]: https://kpt.dev/book/03-packages/08-publishing-a-package