diff --git a/content/concepts/images/v4-nft-2.png b/content/concepts/images/v4-nft-2.png
new file mode 100644
index 00000000..379f67e2
Binary files /dev/null and b/content/concepts/images/v4-nft-2.png differ
diff --git a/content/concepts/v4-nft.md b/content/concepts/v4-nft.md
index 681cf482..8a2eac5e 100644
--- a/content/concepts/v4-nft.md
+++ b/content/concepts/v4-nft.md
@@ -10,13 +10,15 @@ A non-fungible token stored on the blockchain represents a unique asset. NFTs ca
 
 Ocean Protocol defines an [ERC721Factory](https://github.com/oceanprotocol/contracts/blob/v4Hardhat/contracts/ERC721Factory.sol) contract which will allow users to deploy ERC721 contract instances on any of the supported networks. The deployed contract can be associated with Metadata information which describes, also published on-chain. The [Metadata](https://github.com/oceanprotocol/contracts/blob/v4Hardhat/contracts/metadata/Metadata.sol) contract will store the information about the asset, and associated access rights defined through roles.
 
+![Image 1](images/v4-nft-1.png)
+
 ### Combining ERC721 and ERC20
 
 ERC20 interface represents fungible tokens. ERC721 and ERC20 combined together can be used for sub-licensing. These sub-licenses can be traded on any AMM as the underlying contract is ERC20 compliant.
 
 Ocean Protocol's [ERC721Template](https://github.com/oceanprotocol/contracts/blob/v4Hardhat/contracts/templates/ERC721Template.sol) provides functionality to create comibinations of ERC721 and ERC20 contract pairs, each of this pair can represent a different sub-license.
 
-![Image 1](images/v4-nft-1.png)
+![Combining ERC721 and ERC20](images/v4-nft-2.png)
 
 Once the contract is deployed, it will be available on the Ocean Marketplace for trade.