Merge branch 'main' of github.com:flare-foundation/flare-p-chain-indexer

README.md

@@ -103,11 +103,11 @@ mirroring = "0xE64Df6a7e4f4c277C5299f0FE12D7BbB8A207175"    # mirror contract ad
 
 ### Deployment configuration
 
-Configuration files for deployment can be found in [docker/indexer/config_flare.toml](docker/indexer/config_flare_voting.toml) (for mainnet) and [docker/indexer/config_costwo.toml](docker/indexer/config_costwo_voting.toml) (for coston2). Note that database credentials and chain addresses are not included in the config files. You can use these files as a template of your own config files or use the corresponding environment variables to override the given values.
+Configuration files for deployment of the voting client can be found in [docker/indexer/config_flare_voting.toml](docker/indexer/config_flare_voting.toml) (for mainnet) and [docker/indexer/config_costwo_voting.toml](docker/indexer/config_costwo_voting.toml) (for coston2). Note that database credentials and chain addresses are not included in the config files. You can use these files as a template of your own config files or use the corresponding environment variables to override the given values.
 
 You can also use docker-compose to run the indexer. See [docker/indexer/docker-compose.yml](docker/indexer/docker-compose.yml) for an example.
 
-Note that you only need to run voting client. The mirroring client is only needed if you want to mirror the data to the mirror contract (one instance is enough for the whole network).
+Note that you normally only need to run the voting client. The mirroring client is only needed if you want to mirror the data to the mirror contract (one instance is enough for the whole network).
 
 ### Running tests