summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorelisee <elisee@sparklin.org>2013-07-01 17:50:25 +0200
committerelisee <elisee@sparklin.org>2013-07-01 17:50:25 +0200
commitd553ee4c6bf17f14acf06471963859326f8a5f8b (patch)
tree113c44b2b1830e61a2fa5e0554f5304d5f9fd99b
parent85ec26c3f884c2c13021676f7b2a36ac17925178 (diff)
Fix various "it's" -> "its" for Haskell doc
-rw-r--r--haskell.html.markdown6
1 files changed, 3 insertions, 3 deletions
diff --git a/haskell.html.markdown b/haskell.html.markdown
index 1a4cdc67..84b8f263 100644
--- a/haskell.html.markdown
+++ b/haskell.html.markdown
@@ -5,7 +5,7 @@ author_url: http://adit.io
---
Haskell was designed as a practical, purely functional programming language. It's famous for
-it's monads and it's type system, but I keep coming back to it because of it's elegance. Haskell
+its monads and its type system, but I keep coming back to it because of its elegance. Haskell
makes coding a real joy for me.
```haskell
@@ -222,7 +222,7 @@ True :: Bool
-- Here's a function that takes two arguments:
-- add :: Integer -> Integer -> Integer
--- When you define a value, it's good practice to write it's type above it:
+-- When you define a value, it's good practice to write its type above it:
double :: Integer -> Integer
double x = x * 2
@@ -309,7 +309,7 @@ main = do
-- Haskell does IO through a monad because this allows it to be a purely
-- functional language. Our `action` function had a type signature of `IO String`.
-- In general any function that interacts with the outside world (i.e. does IO)
--- gets marked as `IO` in it's type signature. This lets us reason about what
+-- gets marked as `IO` in its type signature. This lets us reason about what
-- functions are "pure" (don't interact with the outside world or modify state)
-- and what functions aren't.