From 2853d9686b2638a4cb47024985f9d8971df6477b Mon Sep 17 00:00:00 2001 From: Janos Gabler Date: Tue, 5 Nov 2024 17:47:39 +0100 Subject: [PATCH] Update docs/source/how_to/how_to_specify_algorithm_and_algo_options.md Co-authored-by: Tim Mensinger --- docs/source/how_to/how_to_specify_algorithm_and_algo_options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/how_to/how_to_specify_algorithm_and_algo_options.md b/docs/source/how_to/how_to_specify_algorithm_and_algo_options.md index ea7313700..54d830cdd 100644 --- a/docs/source/how_to/how_to_specify_algorithm_and_algo_options.md +++ b/docs/source/how_to/how_to_specify_algorithm_and_algo_options.md @@ -12,7 +12,7 @@ There are two ways to specify and configure optimizers. The *optimagic way* and an optimizer and both are super easy to use. As the name suggests, the *scipy way* is more familiar for users of scipy.optimize. The -*optimagic way* has much better discoverability and autocomplete. Using the *optimagic +*optimagic way* adds discoverability and autocomplete. Using the *optimagic way*, you don't need to look things up in the documentation and rarely have to leave your editor, notebook or IDE.