fix typo

docs/src/modules/ROOT/pages/using-timefold-solver/running-the-solver.adoc

@@ -281,7 +281,7 @@ Even `debug` logging can slow down performance considerably for fast stepping al
 (such as Late Acceptance and Simulated Annealing),
 but not for slow stepping algorithms (such as Tabu Search).
 
-Both trace logging and debug logging cause congestion in xref:using-timefold-solver/running-the.solver.adoc#multithreadedSolving[multi-threaded solving] with most appenders,
+Both trace logging and debug logging cause congestion in xref:using-timefold-solver/running-the-solver.adoc#multithreadedSolving[multi-threaded solving] with most appenders,
 see below.
 
 In Eclipse, `debug` logging to the console tends to cause congestion with move evaluation speeds above 10 000 per second.
@@ -391,7 +391,7 @@ logging.config.fileConfig('logging.conf')
 
 [NOTE]
 ====
-When running multiple solvers or a xref:using-timefold-solver/running-the.solver.adoc#multithreadedSolving[multi-threaded solver],
+When running multiple solvers or a xref:using-timefold-solver/running-the-solver.adoc#multithreadedSolving[multi-threaded solver],
 most appenders (including the console) cause congestion with `debug` and `trace` logging.
 Switch to an async appender to avoid this problem or turn off `debug` logging.
 ====