From 144a6165b9bac2208ea38d7e5e1f23fc3a22c679 Mon Sep 17 00:00:00 2001 From: Nigel Tao Date: Fri, 20 Dec 2019 15:24:03 +1100 Subject: [PATCH] Fix "phising" typo --- hello-wuffs-c/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hello-wuffs-c/README.md b/hello-wuffs-c/README.md index 8b19dce2..57289218 100644 --- a/hello-wuffs-c/README.md +++ b/hello-wuffs-c/README.md @@ -76,7 +76,7 @@ run-time checks for integer overflow, but these are typically disabled by default because of the performance impact. Having these checks enabled for developer builds are better than nothing, but it still isn't a complete solution. We don't ship developer builds to our users, and while computer -programmers are better than the average person at e.g. spotting phising +programmers are better than the average person at e.g. spotting phishing attempts, that also means that they can be less likely than the average person to 'test' their developer builds on the malicious input that users encounter.