@@ -176,8 +176,8 @@ There are the following challenges when formatting a module with CPP:
176176 the end. This is much, much harder than simple pretty-printing we want to
177177 do.
178178
179−Here is example that proves that CPP is hard to support if at all possible.
180−Suppose
179+Here is an example that proves that CPP is hard to support if possible at all.
180+Let's suppose that we want to format the following snippet of code:
181181
182182```haskell
183183f = f1
@@ -194,7 +194,7 @@ g = g1
194194#end
195195```
196196
197−After commenting CPP directives:
197+After commenting CPP directives we get:
198198
199199```haskell
200200f = f1
@@ -211,7 +211,7 @@ g = g1
211211{-[#end]-}
212212```
213213
214−After formatting:
214+Then, after formatting we get:
215215
216216```haskell
217217f = f1
@@ -228,7 +228,7 @@ g = g1
228228{-[#end]-}
229229```
230230
231−Output after uncommenting CPP directives:
231+And finally, we uncomment CPP directives:
232232
233233```haskell
234234f = f1
@@ -247,8 +247,8 @@ g = g1
247247
248248Now the definition of `f` is broken when `C1` doesn't hold.
249249
250−Thus CPP should not be supported and if CPP extension is enabled we should
251−signal an error right away.
250+Therefore, CPP should not be supported. If the CPP extension
251+is enabled, we should signal an error right away.
252252
253253### Printing
254254