Merge pull request #6031 from roc-lang/website-typo-fixes

Website typo fixes

www/content/fast.md

@@ -1,6 +1,6 @@
 # Fast
 
-Roc code is designed to build fast and run fast...but what does "fast" mean here? And how close is Roc's curent implementation to realizing that goal?
+Roc code is designed to build fast and run fast...but what does "fast" mean here? And how close is Roc's current implementation to realizing that goal?
 
 ## [Fast programs](#fast-programs) {#fast-programs}
 

www/content/functional.md

@@ -44,7 +44,7 @@ colors
 
 To be fair, direct mutation primitives have benefits too. Some algorithms are more concise or otherwise easier to read when written with direct mutation, and direct mutation can make the performance characteristics of some operations clearer.
 
-As such, Roc's opportunistic mutation design means that data races and reference cycles can be ruled out, and that functions will tend to be more ameanable for chaining, but also that some algorithms will be harder to express, and that performance optimization will likely tend to involve more profiling. These tradeoffs fit well with the language's overall design goals.
+As such, Roc's opportunistic mutation design means that data races and reference cycles can be ruled out, and that functions will tend to be more amenable for chaining, but also that some algorithms will be harder to express, and that performance optimization will likely tend to involve more profiling. These tradeoffs fit well with the language's overall design goals.
 
 ## [No reassignment or shadowing](#no-reassignment) {#no-reassignment}