From f54bdc95bf35813ce2cd6054276941ac84fbeb70 Mon Sep 17 00:00:00 2001 From: Bruno Mendes <61701401+bdmendes@users.noreply.github.com> Date: Sun, 2 Jul 2023 11:49:08 +0100 Subject: [PATCH] Fix readme link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f23910c9..e706971d 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ You can probe the integrity of the engine by running the test suite, which inclu cargo test -Upon developing, to be able to claim a statistically significant improvement over the last version, it is recommended to setup a [tournament](https://www.chessprogramming.org/Chess_Tournaments) between the two versions, using an utility such as [fast-chess](https://github.com/Disservin/fast-chess). It is also possible and fun to deploy the engine to [lichess](https://lichess.org/), through the [lichess-bot bridge](https://github.com/lichess-bot-devs/lichess-bot), although the [Elo](https://en.wikipedia.org/wiki/Elo_rating_system) might not represent the engine's true strength, since it will mostly be based on matchmaking against other engines. +Upon developing, to be able to claim a statistically significant improvement over the last version, it is recommended to setup a tournament between the two versions, using an utility such as [fast-chess](https://github.com/Disservin/fast-chess). It is also possible and fun to deploy the engine to [lichess](https://lichess.org/), through the [lichess-bot bridge](https://github.com/lichess-bot-devs/lichess-bot), although the [Elo](https://en.wikipedia.org/wiki/Elo_rating_system) might not represent the engine's true strength, since it will mostly be based on matchmaking against other engines. ## Usage