diff --git a/KIPs/kip-163.md b/KIPs/kip-163.md
index 8dee5e2c..4954d033 100644
--- a/KIPs/kip-163.md
+++ b/KIPs/kip-163.md
@@ -100,7 +100,7 @@ The features added in CNv3 are only active when PD is enabled; without PD, exist
 | `cancelApprovedStakingWithdrawal`       | Only Multi-sig             | Only PD    |
 | `withdrawApprovedStaking`               | Only Multi-sig             | Only PD    |
 
-The CNv3 must call setPublicDelegation to set public delegation. In `setPublicDelegation`, it deploys a new public delegation contract and connect to CNv3.
+The CNv3 must call `setPublicDelegation` to set public delegation. In `setPublicDelegation`, it deploys a new public delegation contract and connect to CNv3.
 
 The redelegation is a togglable feature, and both current CNv3 and target CNv3 must enable PD and redelegation to use it. Users can redelegate their staking to another CNv3 without waiting for lockup period. But to prevent redelegation hopping, which makes Klaytn's consensus be unstable, users who have been redelegated must wait a lockup period before they can redelegate again. For example, if a user redelegates from [`A` → `B`], then user must wait for a lockup period to redelegate from B to another CNv3. The last redelegation records will be stored in each CNv3s. The below diagram shows how redelegation is processed between CNv3 and PD. The action of PD is discussed in more detail in Public Delegation.
 
diff --git a/assets/kip-163/overview.png b/assets/kip-163/overview.png
index db2e3061..c26d4021 100644
Binary files a/assets/kip-163/overview.png and b/assets/kip-163/overview.png differ