From bed3184b2bf34e3e71819df8319b18fb4dfa74c3 Mon Sep 17 00:00:00 2001
From: jessie-park <160459432+jessie-park@users.noreply.github.com>
Date: Fri, 10 May 2024 11:59:25 +0900
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 9df1027..9c0c0ba 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ It houses configuration files such as ```chain.json``` and ```assetlist.json```,
 ##  ```chain.json```
 A sample chain.json includes the following information.
 ``` {
-  "$schema": "../../chain.schema.json",
+  "$schema": "testnets/initia/chain.json",
   "chain_name": "initia",
   "chain_id": "mahalo-2",
   "website": "<https://initia.xyz>",
@@ -175,7 +175,7 @@ Asset lists are a similar mechanism to allow frontends and other UIs to fetch me
 This standard is a work in progress. You'll notice that the format of assets in the ```assetlist.json``` structure is a strict superset json representation of the banktypes.DenomMetadata from the Cosmos SDK. This is purposefully done so that this standard may eventually be migrated into a Cosmos SDK module in the future, so it can be easily maintained on chain instead of on Github.
 An example assetlist json contains the following structure:
 ```{
-  "$schema": "../../assetlist.schema.json",
+  "$schema": "testnets/initia/assetlist.json",
   "chain_name": "initia",
   "assets": [
     {