From 6d52b3ab5904c1e1c40dab670cec568aaaff50b7 Mon Sep 17 00:00:00 2001 From: FPtje Date: Sun, 1 May 2016 20:54:37 +0200 Subject: [PATCH] wil -> will spelling --- README.MD | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.MD b/README.MD index 0cdb3a6..49e374d 100644 --- a/README.MD +++ b/README.MD @@ -58,4 +58,4 @@ What do I mean by macro-optimisation/the big guys you ask? Think of reducing an That's where the profiler comes in. Always mistrust what you **think** is a big performance hog is, **measure** it. Even the assumptions of people who have optimising code as their profession are often proven wrong by the profiler. Don't be smug and think you can do any better. -When working on performance, the profiler is to be your guide. The profiler is to tell you what to optimise. Do not bother with anything other than the most expensive functions for you wil be wasting your time. +When working on performance, the profiler is to be your guide. The profiler is to tell you what to optimise. Do not bother with anything other than the most expensive functions for you will be wasting your time.