Integrated feedback widget (#690)

* Integrated feedback widget

* Fixed broken links

docs/build/smart-contracts/verify/block-explorers.md

@@ -52,7 +52,7 @@ contract Counter {
 
 :::note
 
-You can check this page for a tutorial on deploying smart contracts using [libraries](../../references/sdk/sdk.md) on Klaytn Baobab Testnet. You may also use a developer tool such as [Hardhat](../get-started/hardhat.md), [Foundry](../smart-contracts/deploy/foundry.md), [Remix](../smart-contracts/deploy/deploy.md#remix-ide)  or another tool if preferred, to deploy the smart contract to Klaytn Baobab Testnet.
+You can check this page for a tutorial on deploying smart contracts using [libraries](../../../references/sdk/sdk.md) on Klaytn Baobab Testnet. You may also use a developer tool such as [Hardhat](../../get-started/hardhat.md), [Foundry](../deploy/foundry.md), [Remix](../deploy/deploy.md#remix-ide)  or another tool if preferred, to deploy the smart contract to Klaytn Baobab Testnet.
 
 :::
 

docs/nodes/service-chain/configure/anchoring.md

@@ -39,7 +39,7 @@ After sending KLAY, you can check the balance like below.
 ```
 
 Then you can enable anchoring via RPC API, `subbridge.anchoring`, like below.
-You can refer to [subbridge APIs](../../../references/service-chain-api/subbridge.md#subbridge_anchoring) for more details.
+You can refer to [subbridge APIs](../../../references/json-rpc/subbridge/anchoring) for more details.
 ```
 > subbridge.anchoring(true)
 true
@@ -51,7 +51,7 @@ You can check the anchored data like below.
 
 ### Sub-Bridge <a id="sub-bridge"></a>
 In Sub-Bridge, You can check the latest anchored block number like below.
-You can refer to [subbridge APIs](../../../references/service-chain-api/subbridge.md#subbridge_latestAnchoredBlockNumber) for more details.
+You can refer to [subbridge APIs](../../../references/json-rpc/subbridge/latest-anchored-block-number) for more details.
 ```javascript
 > subbridge.latestAnchoredBlockNumber
 71025
@@ -65,7 +65,7 @@ Also, you can find the anchoring transaction hash by the service chain block num
 
 ### Main-Bridge <a id="sub-bridge"></a>
 In Main-Bridge, if chain indexing option is enabled, you can find the anchoring tx hash by a service chain block hash like below.
-You can refer to [mainbridge APIs](../../../references/service-chain-api/mainbridge.md#mainbridge_convertChildChainBlockHashToParentChainTxHash) for more details.
+You can refer to [mainbridge APIs](../../../references/json-rpc/mainbridge/convert-child-chain-block-hash-to-parent-chain-tx-hash) for more details.
 
 ```javascript
 > mainbridge.convertChildChainBlockHashToParentChainTxHash("0xeadc6a3a29a20c13824b5df1ba05cca1ed248d046382a4f2792aac8a6e0d1880")

docs/nodes/service-chain/configure/bridge-configuration.md

@@ -77,7 +77,7 @@ at block: 11573551 (Wed, 13 Feb 2019 07:12:52 UTC)
 
 #### Get the EN's KNI <a id="get-the-ens-kni"></a>
 
-After attaching to the process via IPC, you can check the EN's main-bridge KNI like below. You can refer to [Service Chain API](../../../references/service-chain-api/subbridge.md).
+After attaching to the process via IPC, you can check the EN's main-bridge KNI like below. You can refer to [Service Chain API](../../../references/json-rpc/subbridge/add-peer).
 
 ```javascript
 > mainbridge.nodeInfo

docs/nodes/service-chain/configure/value-transfer.md

@@ -77,7 +77,7 @@ instance: Klaytn/vvX.X.X/XXXX-XXXX/goX.X.X
 "0x5C1C757a6Cb6c6FcEFE398674D8209FDA2A74Df4"
 ```
 
-You can refer to the [subbridge API](../../../references/service-chain-api/subbridge.md#subbridge_parentOperator) for more details.
+You can refer to the [subbridge API](../../../references/json-rpc/subbridge/parent-operator) for more details.
 
 ### Send KLAY to Bridge Operators <a id="send-klay-to-bridge-operators"></a>
 Like anchoring, the parent chain bridge operator needs KLAY to make a value-transfer transaction.
@@ -142,7 +142,7 @@ instance: Klaytn/vvX.X.X/XXXX-XXXX/goX.X.X
 }]
 ```
 
-You can refer to the [subbridge API](../../../references/service-chain-api/subbridge.md#subbridge_deployBridge) for more details.
+You can refer to the [subbridge API](../../..references/json-rpc/subbridge/deploy-bridge) for more details.
 
 `subbridge_listBridge` shows the bridge contract addresses and their subscription status.
 Sub-bridge saves the list of bridge contract addresses in a file. On reboot, sub-bridge reloads the bridge contract list from the file.
@@ -195,7 +195,7 @@ Each value means like below
 
 ### RPC API <a id="rpc-api"></a>
 You can check the status of a bridge contract like below.
-You can refer to the [subbridge API](../../../references/service-chain-api/subbridge.md#subbridge_getBridgeInformation) for more details.
+You can refer to the [subbridge API](../../../references/json-rpc/subbridge/get-bridge-information) for more details.
 
 ```javascript
 > subbridge.getBridgeInformation("0x27caeba831d98b5fbb1d81ce0ed20801702f443a")
@@ -231,7 +231,7 @@ null
 
 This command registers the child chain token ("0x376b72abe1b29cace831bd3f5acdfa967814c9cd") with the child chain bridge contract ("0x27caeba831d98b5fbb1d81ce0ed20801702f443a"). And the parent chain token ("0x53160735f7cc6ff75e48619f368bb94daff66a1b") with the parent chain bridge contract ("0x22c41ae528627b790233d2e59ea520be12350eb5").
 
-You can refer to the [Service Chain API](../../../references/service-chain-api/subbridge.md#subbridge_registerToken) for more details.
+You can refer to the [Service Chain API](../../../references/json-rpc/subbridge/register-token) for more details.
 
 ## Request Value Transfer <a id="request-value-transfer"></a>
 This section explains the contract methods that will be invoked by a user to request a value transfer.