diff --git a/content/technical/2011/12/ios-launch-image-is-not-a-splashscreen.html b/content/technical/2011/12/ios-launch-image-is-not-a-splashscreen.html
index 5e96504..57d6875 100644
--- a/content/technical/2011/12/ios-launch-image-is-not-a-splashscreen.html
+++ b/content/technical/2011/12/ios-launch-image-is-not-a-splashscreen.html
@@ -1,13 +1,15 @@
 At work we're currently having an iOS app that I'm working on styled
 by a designer. The second screen we were supplied was a pretty splash
-screen with a big logo on it. We responded saying that we didn't want to
-use Default.png like that. Our designer responded saying that was fine
-but most clients were after TODO so he does one by default. This is
-silly as it is not the intended use for the launch image.
+screen with a big logo on it. We responded saying that we didn't want
+to use the launch image like that. Our designer responded saying that
+was fine but the majority of the clients nowadays require heavy emphases
+on corporate branding therefore it was a standard practice to cater to
+those requirements. It's a shame that this is what people are are asking
+for since its is not the intended use of the launch image.
 
-Justin Williams recently had the following to say on the topic of splash
-screens in his [On Magazines and the iPad][carpeaqua] article (emphasis
-from the article):
+Justin Williams recently had the following clear-cut words to say on the
+topic of splash screens in his [On Magazines and the iPad][carpeaqua]
+article (emphasis from the article):
 
 > Remember, kids. The first rule of mobile development is that *no one
 > gives a fuck about your brand*. A splash screen with a giant logo