diff --git a/docs/content/en/docs-dev/migrating-from-v0-to-v1/_index.md b/docs/content/en/docs-dev/migrating-from-v0-to-v1/_index.md
index 6ed0c9ae24..ea0b50df89 100644
--- a/docs/content/en/docs-dev/migrating-from-v0-to-v1/_index.md
+++ b/docs/content/en/docs-dev/migrating-from-v0-to-v1/_index.md
@@ -1,6 +1,6 @@
 ---
-title: "Migrating to PipeCD V1"
-linkTitle: "Migrating to PipeCD V1"
+title: "Migrate to PipeCD V1"
+linkTitle: "Migrate to PipeCD V1"
 weight: 90
 description: >
   Documentation on migrating your application from PipeCD V0 to V1
@@ -8,6 +8,8 @@ description: >
 
 This page explains how to safely migrate your existing PipeCD System to the RC version of **PipeCD V1**, the new plugin-based architecture that brings modularity and extensibility to PipeCD.
 
+Incase you are using PipeCD V0, follow the setps on this page to migrate to **PipeCD V1**.
+
 ## Overview
 
 PipeCD V1 introduces a **pluggable architecture** that allows developers to add and maintain custom deployment and operational plugins without modifying the core system of PipeCD.
@@ -97,7 +99,7 @@ Or specify an entire directory:
 pipectl migrate application-config --dirs=path/to/apps/
 ```
 
-Here is an example for a simple app.pipecd.yaml file which demonstrates a Kubernetes deployment and simulates a 30s wait:
+Here is an example for a simple app.pipecd.yaml file which demonstrates a kubernetes deployment and simulates a 30s wait:
 
 ```yaml
 apiVersion: pipecd.dev/v1beta1
diff --git a/docs/content/en/docs-v1.0.x/migrating-from-v0-to-v1/_index.md b/docs/content/en/docs-v1.0.x/migrating-from-v0-to-v1/_index.md
index 2e1d92acc3..ea0b50df89 100644
--- a/docs/content/en/docs-v1.0.x/migrating-from-v0-to-v1/_index.md
+++ b/docs/content/en/docs-v1.0.x/migrating-from-v0-to-v1/_index.md
@@ -6,7 +6,7 @@ description: >
   Documentation on migrating your application from PipeCD V0 to V1
 ---
 
-This page explains how to safely migrate your existing PipeCD System to the RC version of **PipeCD V1**, the new plugin-based architecture that brings modularity and extensibility to PipeCD. 
+This page explains how to safely migrate your existing PipeCD System to the RC version of **PipeCD V1**, the new plugin-based architecture that brings modularity and extensibility to PipeCD.
 
 Incase you are using PipeCD V0, follow the setps on this page to migrate to **PipeCD V1**.
 
@@ -99,7 +99,7 @@ Or specify an entire directory:
 pipectl migrate application-config --dirs=path/to/apps/
 ```
 
-Here is an example for a simple app.pippcd.yaml file which demonstrates a kubernetes deployment and simulates a 30s wait:
+Here is an example for a simple app.pipecd.yaml file which demonstrates a kubernetes deployment and simulates a 30s wait:
 
 ```yaml
 apiVersion: pipecd.dev/v1beta1
@@ -300,4 +300,4 @@ Simply **stop** the running `pipedv1` instance, then **start** the `pipedv0` ser
 
 Once restarted, the old `pipedv0` should resume operation using its previous configuration and state. Happy Pipe-CDing!
 
----
\ No newline at end of file
+---