Use proper markdown heading syntax instead of emphasis

Author: m-Peter

README.md

@@ -2,7 +2,7 @@
 
 # EVM Gateway
 
-**EVM Gateway enables seamless interaction with EVM on Flow, mirroring the experience of engaging with any other EVM blockchain.**
+## EVM Gateway enables seamless interaction with EVM on Flow, mirroring the experience of engaging with any other EVM blockchain
 
 EVM Gateway implements the Ethereum JSON-RPC API for [EVM on Flow](https://developers.flow.com/evm/about) which conforms to the Ethereum [JSON-RPC specification](https://ethereum.github.io/execution-apis/api-documentation/). The EVM Gateway is tailored for integration with the EVM environment on the Flow blockchain. Rather than implementing the full `geth` stack, the JSON-RPC API available in EVM Gateway is a lightweight implementation that uses Flow's underlying consensus and smart contract language, [Cadence](https://cadence-lang.org/docs/), to handle calls received by the EVM Gateway. For those interested in the underlying implementation details, please refer to the [FLIP #243](https://github.com/onflow/flips/issues/243) (EVM Gateway) and [FLIP #223](https://github.com/onflow/flips/issues/223) (EVM on Flow Core) improvement proposals.
 
@@ -23,7 +23,7 @@ The basic design of the EVM Gateway is as follows:
 
 # Building
 
-**Build from source**
+## Build from source
 
 ```bash
 # Make sure you pull the latest changes before running `make build`
@@ -76,7 +76,7 @@ It is acceptable to create a single Cadence account for the COA and use the EVM
 
 For local development, first install [Flow CLI](https://developers.flow.com/tools/flow-cli/install). The examples below require no configuration and are intended for local development.
 
-**Run from CLI**
+### Run from CLI
 
 Before running the gateway locally you need to start the Flow Emulator:
 
@@ -96,7 +96,7 @@ make start-local
 Note that the gateway will be starting from the latest emulator block, so if the emulator is run before any transactions happen in the meantime, the gateway will not fetch those historical blocks & transactions.
 This will be improved soon.
 
-**Run with Docker**
+### Run with Docker
 
 Using Docker for local development is also supported. The following target builds the current source directory into a docker image
 
@@ -108,7 +108,7 @@ This target starts the flow emulator and then runs the EVM Gateway using the ima
 make docker-run-local
 ```
 
-**Verify**
+## Verify
 
 To verify the service is up and running:
 
@@ -131,7 +131,7 @@ it should return:
 Running against the testnet with a local build can be done by pointing the gateway to the testnet ANs and providing the correct configuration.
 Please refer to the configuration section and read through all the configuration flags before proceeding.
 
-**Create Flow account to use for COA**
+### Create Flow account to use for COA
 
 If you don't already have a Flow account you will need to create account keys using the following command. 
 
@@ -153,7 +153,7 @@ Signature Algorithm 	 ECDSA_P256
 Then visit https://faucet.flow.com/, and use the generated `Public Key`, to create and fund your Flow testnet account.
 Make sure to use the Flow address and the `Private Key` for the `--coa-address` & `--coa-key` flags.
 
-**Run EVM Gateway connected to Testnet**
+### Run EVM Gateway connected to Testnet
 
 Below is an example configuration for running against testnet, with a preconfigured testnet account.
 
@@ -191,7 +191,7 @@ Should return a response similar to:
 }
 ```
 
-**Run local EVM GW docker container connected to Testnet**
+### Run local EVM GW docker container connected to Testnet
 
 To use the `make` target to connect a container based gateway instance to testnet requires the following environment variables to be set. 
 
@@ -294,14 +294,14 @@ To connect using Websockets you can use the same DNS names as above but change `
 # JSON-RPC API
 The EVM Gateway implements APIs according to the Ethereum specification: https://ethereum.org/en/developers/docs/apis/json-rpc/#json-rpc-methods.
 
-**Additional APIs**
+## Additional APIs
 - Tracing APIs allows you to fetch execution traces
     * `debug_traceTransaction`
     * `debug_traceBlockByNumber`
     * `debug_traceBlockByHash`
 - `debug_flowHeightByBlock` - returns the flow block height for the given EVM block (id or height)
 
-**Unsupported APIs**
+## Unsupported APIs
 - Wallet APIs: we don't officially support wallet APIs (`eth_accounts`, `eth_sign`, `eth_signTransaction`, `eth_sendTransaction`) due to security
   concerns that come with managing the keys on production environments, however, it is possible to configure the gateway to allow these
   methods for local development by using a special flag `--wallet-api-key`.