From 5185e4b284e60767b2c0fcad708472f582775eae Mon Sep 17 00:00:00 2001 From: Moein zargarzadeh Date: Fri, 31 May 2024 11:29:49 +0330 Subject: [PATCH] fix docs --- docs/keygen-service/keygen-docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/keygen-service/keygen-docker.md b/docs/keygen-service/keygen-docker.md index 1d08efe..e1d2721 100644 --- a/docs/keygen-service/keygen-docker.md +++ b/docs/keygen-service/keygen-docker.md @@ -80,7 +80,7 @@ docker compose up # use `docker-compose up` for older versions of Docker ``` > **Note:** -> Each guard has a unique peerId that you should provide to the moderator of the keygen ceremony. Your peerId will be whitelisted relays. Upon starting your guard or keygen-service for the first time, you can find the value of this parameter in your guard's logs or keygen-service's logs. For example, you should see a line like this in your log file located at `./keygen-service/logs/keygen-logs/` or ./guard/logs/guard-logs/ or in your console: +> Each guard has a unique peerId that you should provide to the moderator of the keygen ceremony. Your peerId will be whitelisted in relays. Upon starting your guard or keygen-service for the first time, you can find the value of this parameter in your guard's logs or keygen-service's logs. For example, you should see a line like this in your log file located at `./keygen-service/logs/keygen-logs/` or ./guard/logs/guard-logs/ or in your console: > ``` > info: Dialer node started with peerId: 12D3KooWNGaHx3EAdNeKUFxAKrg3EyKFN8gHHw9H5ZiBmRVjxHpG. > ```