Merge pull request #779 from bwignall/typo
Fix typos
commit08265cc3585bac5c50709fe75cd4eddfbaa9218d
authorMichael Snoyman <michael@snoyman.com>
dateSun 1 Dec 2019, 06:35 (7 years ago)
parenta07c4aed996501
wai-app-static/Network/Wai/Application/Static.hs+1−1
@@ -167,7 +167,7 @@ serveFile StaticSettings {..} req file
167167 -- Note: It would be arguably better to next check
168168 -- if-modified-since and return a 304 if that indicates a match as
169169 -- well. However, the circumstances under which such a situation
170− -- could arise would be very anomolous, and should likely warrant a
170+ -- could arise would be very anomalous, and should likely warrant a
171171 -- new file being sent anyway.
172172 (Just hash, _) -> respond [("ETag", hash)]
173173
wai-app-static/test/WaiAppStaticTest.hs+1−1
@@ -57,7 +57,7 @@ spec = do
5757 assertStatus 200 =<<
5858 request (setRawPathInfo defRequest path)
5959
60− it "404 for non-existant files" $ webApp $
60+ it "404 for non-existent files" $ webApp $
6161 assertStatus 404 =<<
6262 request (setRawPathInfo defRequest "doesNotExist")
6363
wai-extra/Network/Wai/EventSource/EventStream.hs+1−1
@@ -1,5 +1,5 @@
11{-# LANGUAGE CPP #-}
2−{- code adapted by Mathias Billman originaly from Chris Smith https://github.com/cdsmith/gloss-web -}
2+{- code adapted by Mathias Billman originally from Chris Smith https://github.com/cdsmith/gloss-web -}
33
44{-|
55 Internal module, usually you don't need to use it.
wai-websockets/server.lhs+1−1
@@ -101,7 +101,7 @@ stays alive on some browsers.
101101> conn <- WS.acceptRequest pending
102102> WS.forkPingThread conn 30
103103
104−When a client is succesfully connected, we read the first message. This should
104+When a client is successfully connected, we read the first message. This should
105105be in the format of "Hi! I am Jasper", where Jasper is the requested username.
106106
107107> msg <- WS.receiveData conn
warp/Network/Wai/Handler/Warp.hs+1−1
@@ -378,7 +378,7 @@ setProxyProtocolRequired y = y { settingsProxyProtocol = ProxyProtocolRequired }
378378--
379379-- WARNING: This is contrary to the PROXY protocol specification and
380380-- using it can indicate a security problem with your
381−-- architecture if the web server is directly accessable
381+-- architecture if the web server is directly accessible
382382-- to the public, since it would allow easy IP address
383383-- spoofing. However, it can be useful in some cases,
384384-- such as if a load balancer health check uses regular
warp/test/ResponseSpec.hs+1−1
@@ -83,7 +83,7 @@ spec = do
8383 it "discards empty lines" $ do
8484 sanitizeHeaderValue "foo\r\n\r\nbar" `shouldBe` "foo\r\n bar"
8585
86− context "when sanitizing single occurences of \n" $ do
86+ context "when sanitizing single occurrences of \n" $ do
8787 it "replaces \n with \r\n" $ do
8888 sanitizeHeaderValue "foo\n bar" `shouldBe` "foo\r\n bar"
8989