diff --git a/README.md b/README.md
index 993ff68..4bf18e6 100644
--- a/README.md
+++ b/README.md
@@ -110,7 +110,7 @@ The protocol used in SINE Benchmark can be illustrated by this simple example:
 
 As in the example, the CLI tool takes a set of values (defined in a json to be provided by the user) and for each of the values generates a number of random shares identical to the number of other participants.
 
-When they join a benchmarking session, each participant is given a public and a private key. These will be used to **encrypt** each share with the public key of the recipient and **sign** the share with the private key of the sender.
+When they join a benchmarking session, each participant generates a public and a private key. These will be used to **encrypt** each share with the public key of the recipient and **sign** the share with the private key of the sender.
 
 Once in possession of all shares, each participant can add them to their secret share (i.e., the result of subtracting the shares to their private value) yielding their sum. Sums cannot be traced back to the private values of participants and are, therefore, sent as plain text.
 
@@ -124,4 +124,4 @@ It uses [libp2p](https://github.com/libp2p/rust-libp2p), two protocols in partic
   - [upnp](https://github.com/libp2p/rust-libp2p/tree/master/examples/upnp)
   - [gossipsub](https://github.com/libp2p/specs/tree/master/pubsub/gossipsub)
 
-The first participant will forward the (encrypted) messages using `gossipsub` to the full group of connected peers. The connection to the first participant is established using `upnp`, which needs to be supported and enabled by the network and router of the participant.
\ No newline at end of file
+The first participant will forward the (encrypted) messages using `gossipsub` to the full group of connected peers. The connection to the first participant is established using `upnp`, which needs to be supported and enabled by the network and router of the participant.