From e17999f19b4c52b7066d0074a7fb20ecc958d113 Mon Sep 17 00:00:00 2001 From: Alex Mellnik Date: Tue, 11 Jun 2019 22:09:59 -0700 Subject: [PATCH] Two minor typos --- docs/src/performance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/performance.md b/docs/src/performance.md index 00b94a9d..682b7231 100644 --- a/docs/src/performance.md +++ b/docs/src/performance.md @@ -18,7 +18,7 @@ And you use less memory. Not only should your activation functions be [type-stable](https://docs.julialang.org/en/v1/manual/performance-tips/#Write-%22type-stable%22-functions-1), they should also preserve the type of their inputs. -A very artificial example using an activatioon function like +A very artificial example using an activation function like ``` my_tanh(x) = Float64(tanh(x)) @@ -73,4 +73,4 @@ end ``` When doing this kind of concatenation use `reduce(hcat, xs)` rather than `hcat(xs...)`. -This will avoid the splatting penality, and will hit the optimised `reduce` method. +This will avoid the splatting penalty, and will hit the optimised `reduce` method.