diff --git a/README.md b/README.md index 023c6c4..f072d82 100644 --- a/README.md +++ b/README.md @@ -197,7 +197,7 @@ The instructions for **building the tool from the source code** contained in thi ## Reproducing Experimental Results To reproduce the results of the evaluation shown in the paper using Docker, you may simply repeat the process described above for the 9 smart contracts used in the experiments: `xForce`, `iToken`, `cToken`, `Value`, `Uranium`, `Unprotected`, `Refund_NoSub`, `Confused_Sign`, `EtherBank`. -Please note that while most of the smart contracts are usually repaired in under 1 minute, `Uranium` may take several minutes to be processed (due to the non-linear arithemtic expressions used in a smart contract, which SMT solvers struggle with). +Please note that while most of the smart contracts are usually repaired in under 1 minute, `Uranium` may take several minutes to be processed (due to the non-linear arithemtic expressions used in a smart contract, which SMT solvers struggle with). For the `cToken`, two correct and conditionally equivalent patches are identified—in this case, the first, simpler, patch is preferable. The commands to be run would look as follows: