fixing write file vs iceberg saving

Author: Ducasse

Chapters/FirstApplication/FirstApplication.pillar

@@ -379,13 +379,13 @@ First, do not stress! It's perfectly normal to make a mess of things when you pr
 
 Now that you have ""Lights Out"" working, you probably want to save it somewhere so that you can archive it and share it with your friends. Of course, you can save your whole Pharo image and show off your first program by running it, but your friends probably have their own code in their images, and don't want to give that up to use your image. What you need is a way of getting the source code out of your Pharo image so that other programmers can bring it into theirs.
 
-We showed you the basics of using Iceberg and Git to save, share, and version your projects, and you should feel free to do that again with Lights Out. If you would like to learn more about Iceberg, and you're feeling impatient, then you should feel free to skip ahead to Chapter *@cha:Iceberg*.
+When developing the counter example, we showed you the basics of using Iceberg and Git to save, share, and version your projects, and you should really do the same with Lights Out. Using Git to save Pharo code is the best solution. If you would like to learn more about Iceberg, and you're feeling impatient, then you should feel free to skip ahead to Chapter *@cha:Iceberg*.
 
-If you're still reading this, we're now going to take a look at exporting your Pharo code as files.
+!!!Writing code to files
 
-!!!Saving code in a file
-
-You can also save the code of your package by writing it to a file, an action commonly called "filing out" by all Pharoers, Squeakers and related communities. The right-click menu in the Package pane will give you the option to select ""Extra > File Out"" the whole of the ==PBE-LightsOut== package. The resulting file is more or less human readable, but is really intended for computers, not humans. You can email this file to your friends, and they can "file it in" with their own image.
+While saving your code with Git is the best way to do it, Pharo also offers a way to write code to files on your disc. 
+It is rudimentary and does not actually version the code but it can be handy on certain occasions. 
+You can also save the code of your package by writing it to a file, an action commonly called "filing out" by all Pharoers and related communities. The right-click menu in the Package pane will give you the option to select ""Extra > File Out"" the whole of the ==PBE-LightsOut== package. The resulting file is more or less human readable, but is really intended for computers, not humans. You can email this file to your friends, and they can "file it in" with their own image.
 
 +File out the ==PBE-LightsOut== package.>file://figures/fileOut.png|width=85|label=fig:fileOut+