From a55878453c9dfb499411872f4313facbe0b613cd Mon Sep 17 00:00:00 2001 From: Dhairya Gandhi Date: Thu, 10 Oct 2019 20:16:29 +0530 Subject: [PATCH] typo Co-Authored-By: Mike J Innes --- docs/src/training/optimisers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/training/optimisers.md b/docs/src/training/optimisers.md index 2d195191..e3178504 100644 --- a/docs/src/training/optimisers.md +++ b/docs/src/training/optimisers.md @@ -94,7 +94,7 @@ Flux internally calls on this function via the `update!` function. It shares the ## Composing Optimisers -Flux defines a special kind of optimiser called simply as `Optimiser` which takes in a arbitrary optimisers as input. Its behaviour is similar to the usual optimisers, but differs in that it acts by calling the optimsers listed in it sequentially. Each optimiser produces a modified gradient +Flux defines a special kind of optimiser called simply as `Optimiser` which takes in a arbitrary optimisers as input. Its behaviour is similar to the usual optimisers, but differs in that it acts by calling the optimisers listed in it sequentially. Each optimiser produces a modified gradient that will be fed into the next, and the resultant update will be applied to the parameter as usual. A classic use case is where adding decays is desirable. Flux defines some basic decays including `ExpDecay`, `InvDecay` etc. ``julia