fix debug

Author: JukLee0ira

docs/xdc/debug/debug.md

@@ -4,7 +4,7 @@
 
 The `debug` API gives you access to several non-standard RPC methods, which will allow you to inspect, debug and set certain debugging flags during runtime.
 
-### debug_blockProfile%
+### debug_blockProfile
 
 The `blockProfile` method turns on block profiling for the given duration and writes profile data to disk. It uses a profile rate of 1 for most accurate information. If a different rate is desired, set the rate and write the profile manually using debug_writeBlockProfile.
 
@@ -38,7 +38,7 @@ Response:
 ```
 
 
-### debug_chaindbCompact%
+### debug_chaindbCompact
 
 The `chaindbCompact` method flattens the entire key-value database into a single level, removing all unused slots and merging all keys.
 
@@ -67,7 +67,7 @@ Response:
 ```
 
 
-### debug_chaindbProperty%
+### debug_chaindbProperty
 
 The `chaindbProperty` method returns leveldb properties of the key-value database.
 
@@ -87,7 +87,7 @@ curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
   "id": 1001,
   "method": "debug_chaindbProperty",
   "params": [
-    ""
+    "leveldb.stats"
   ]
 }' | jq
 ```
@@ -137,7 +137,7 @@ Response:
 ```
 
 
-### debug_dbGet%
+### debug_dbGet
 
 The `dbGet` method returns the raw value of a key stored in the database.
 
@@ -297,7 +297,7 @@ Response:
 ```
 
 
-### debug_getModifiedAccountsByHash%
+### debug_getModifiedAccountsByHash
 
 The `getModifiedAccountsByHash` method returns all accounts that have changed between the two blocks specified. A change is defined as a difference in nonce, balance, code hash, or storage hash. With one parameter, returns the list of accounts modified in the specified block.
 
@@ -368,7 +368,7 @@ Response:
 ```
 
 
-### debug_goTrace%
+### debug_goTrace
 
 The `goTrace` method turns on Go runtime tracing for the given duration and writes trace data to disk.
 
@@ -462,7 +462,7 @@ Response:
 See [debug_memStats_response.json](./debug_memStats_response.json)
 
 
-### debug_mutexProfile%
+### debug_mutexProfile
 
 The `mutexProfile` method turns on mutex profiling for nsec seconds and writes profile data to file. It uses a profile rate of 1 for most accurate information. If a different rate is desired, set the rate and write the profile manually.
 
@@ -496,7 +496,7 @@ Response:
 ```
 
 
-### debug_preimage%
+### debug_preimage
 
 The `preimage` method returns the preimage for a sha3 hash, if known.
 
@@ -672,7 +672,7 @@ Response:
 ```
 
 
-### debug_setHead%
+### debug_setHead
 
 The `setHead` method sets the current head of the local chain by block number. Note, this is a destructive action and may severely damage your chain. Use with extreme caution.
 
@@ -869,7 +869,7 @@ Response:
 ```
 
 
-### debug_storageRangeAt%
+### debug_storageRangeAt
 
 The `storageRangeAt` method returns the storage at the given block height and transaction index. The result can be paged by providing a maxResult to cap the number of storage slots returned as well as specifying the offset via keyStart (hash of storage key).
 
@@ -902,7 +902,7 @@ Response:
 ```
 
 
-### debug_traceBlock%
+### debug_traceBlock
 
 The `traceBlock` method will return a full stack trace of all invoked opcodes of all transaction that were included in this block. Note, the parent of this block must be present or it will fail. For the second parameter see TraceConfig reference.
 
@@ -999,7 +999,7 @@ Response:
 See [debug_traceBlockByNumber_response.json](./debug_traceBlockByNumber_response.json)
 
 
-### debug_traceBlockFromFile%
+### debug_traceBlockFromFile
 
 The `traceBlockFromFile` meothod accepts a file containing the RLP of the block.
 
@@ -1079,7 +1079,7 @@ Response:
 ```
 
 
-### debug_traceTransaction%
+### debug_traceTransaction
 
 The `traceTransaction` method debugging method will attempt to run the transaction in the exact same manner as it was executed on the network. It will replay any transaction that may have been executed prior to this one before it will finally attempt to execute the transaction that corresponds to the given hash.